commit-staged — Claude Code skill: what it does, how to install
commit-staged automates commit creation: checks staged diffs, runs /simplify on code edits, and writes conventional commits using session rationale.
Apache-2.0 ★ 1,216 updated 2026-11-09
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install github-dev@claude-settingsWhat commit-staged does
The skill inspects changes in the staging area via git diff --cached and completely ignores unstaged files. Before writing the message, it runs the /simplify skill on the staged diff. Diffs containing only documentation skip this step. When subagent execution is supported, the entire flow delegates to github-dev:commit-creator.
Commit messages follow conventional types like feat, fix, refactor, or docs. The summary line stays under 50 characters. Instead of reciting raw code diffs, the message explains the intent by extracting reasoning directly from the conversation history. Execution runs via HEREDOC formatting.
The routine also checks README.md against staged changes to capture new features or setup instructions for added dependencies. Test plans are intentionally left out of the final message.
What it helps with
- create conventional commits from staged diffs
- run
/simplifyon code changes prior to committing - synchronize
README.mdwith newly introduced dependencies - embed conversation context and rationale into commit descriptions
Example prompts for the agent
- commit these changes
- commit-staged: explain why the cache layer was replaced
- stage and commit
How to install commit-staged
1Plugin marketplace
/plugin marketplace add fcakyon/claude-codex-settings/plugin install github-dev@claude-settingsThis installs the whole github-dev plugin with all its skills
2Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill commit-staged -a claude-code3Manually: put the files in place
~/.claude/skills/commit-staged/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/commit-staged/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill commit-staged -a codex2Manually: put the files in place
.agents/skills/commit-staged/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill commit-staged -a cursor2Manually: put the files in place
.cursor/skills/commit-staged/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install fcakyon/claude-codex-settings plugins/github-dev/skills/commit-staged2Manually: put the files in place
.github/skills/commit-staged/SKILL.md1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill commit-staged -a gemini-cli2Platform CLI
gemini skills install https://github.com/fcakyon/claude-codex-settings --path plugins/github-dev/skills/commit-stagedManually: put the files in place
.devin/skills/commit-staged/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about commit-staged
How to install commit-staged in Claude Code?
First add the marketplace repository with /plugin marketplace add fcakyon/claude-codex-settings, then run /plugin install github-dev@claude-settings.
What does commit-staged do?
It reads staged diffs, executes /simplify, checks documentation parity, and writes conventional commit messages with short subject lines.
Does commit-staged inspect unstaged changes?
No. The skill reads only git diff --cached and leaves unstaged files untouched.
Source text
SKILL.md · Apache-2.0
---
name: commit-staged
description: This skill should be used when user asks to "commit these changes", "write commit message", "stage and commit", "create a commit", "commit staged files", or explicitly invokes "commit-staged".
---
# Commit Staged
Complete workflow for creating commits following project standards.
When explicitly invoked with extra text, treat that text as additional context about the
changes and include it in commit planning and commit messages.
When session history includes findings, motivation, or rationale, include the strongest
points in the commit message body instead of relying on the diff alone.
## Process
**First, run the `/simplify` skill on the staged diff and apply its findings before committing, docs-only commits included.**
1. **Preferred execution**
- If subagents are available, use `github-dev:commit-creator` for the full workflow.
- Pass along any extra invocation text as additional context.
- Otherwise follow the manual steps below.
2. **Analyze staged files only**
- Check all staged files: `git diff --cached --name-only`
- Read diffs: `git diff --cached`
- Completely ignore unstaged changes
3. **Commit message format**
- First line: `{type}: brief description` (max 50 chars)
- Types: `feat`, `fix`, `refactor`, `docs`, `style`, `test`, `build`
- Use plain language. Avoid jargon, buzzwords, and repo shorthand unless an exact command or tool name is needed.
- Use findings and motivation from session history when available.
- Focus on 'why' not 'what'
- 1 sentence conventional style + 1-2 short motivation/findings sentences if possible
- For complex changes, add bullet points after blank line
4. **Message examples**
- `feat: add sign-in flow`
- `fix: stop duplicate jobs on save`
- `docs: add skills install snippets`
5. **Documentation update**
- Check README.md for:
- New features that should be documented
- Outdated descriptions no longer matching implementation
- Missing setup instructions for new dependencies
- Update as needed based on staged changes
6. **Execution**
- Commit uses HEREDOC syntax for proper formatting
- Verify commit message has correct format
- Don't add test plans to commit messages
## Best Practices
- Analyze staged files before writing message
- Keep first line under 50 chars
- Use active voice in message
- Use simple words that still stay accurate
- Prefer session findings over repeating raw diff details
- One logical change per commit
- Ensure README reflects implementation
© Fatih C. Akyon · Apache-2.0 · fcakyon/claude-codex-settings