Agent Skills
› fcakyon/claude-codex-settings
› commit-staged
commit-staged
GitHub指导完成代码暂存与提交工作流的技能。分析已暂存文件，遵循约定式提交规范生成消息，更新文档，并执行最终提交操作。
Trigger Scenarios
commit these changes
write commit message
stage and commit
create a commit
commit staged files
Install
npx skills add fcakyon/claude-codex-settings --skill commit-staged -g -y
SKILL.md
Frontmatter
{
"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 diffs are a no-op.
-
Preferred execution
- If subagents are available, use
github-dev:commit-creatorfor the full workflow. - Pass along any extra invocation text as additional context.
- Otherwise follow the manual steps below.
- If subagents are available, use
-
Analyze staged files only
- Check all staged files:
git diff --cached --name-only - Read diffs:
git diff --cached - Completely ignore unstaged changes
- Check all staged files:
-
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
- First line:
-
Message examples
feat: add sign-in flowfix: stop duplicate jobs on savedocs: add skills install snippets
-
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
- Check README.md for:
-
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
Version History
- 9d0ce8b Current 2026-07-25 10:34
