commit
GitHub分析暂存区代码变更，生成符合 Conventional Commits 规范的提交信息。支持多种类型（如 feat、fix、refactor），并遵循主题、正文和页脚的格式规则，提升 Git 提交标准化程度。
Trigger Scenarios
需要为当前暂存的代码更改生成 Git 提交信息时
希望自动化或辅助编写标准化的 commit message 时
Install
npx skills add FlorianBruniaux/claude-code-ultimate-guide --skill commit -g -y
SKILL.md
Frontmatter
{
"name": "commit",
"effort": "low",
"description": "Generate a conventional commit message for staged changes",
"when_to_use": "Use when ready to commit staged changes and need a conventional commit message.",
"argument-hint": "[--amend] [message]",
"disable-model-invocation": true
}
Conventional Commit
Generate a conventional commit message for staged changes.
Instructions
- Run
git diff --cachedto see staged changes - Analyze the nature of changes
- Generate a commit message following the format below
Commit Format
<type>(<scope>): <subject>
[optional body]
[optional footer]
Types
feat: New featurefix: Bug fixdocs: Documentation onlystyle: Formatting, missing semicolons, etc.refactor: Code change that neither fixes nor adds featureperf: Performance improvementtest: Adding missing testschore: Maintenance tasks
Rules
- Subject: imperative mood, no period, max 50 chars
- Body: explain WHAT and WHY, not HOW
- Footer: breaking changes, issue references
Examples
feat(auth): add password reset functionality
Implement password reset flow with email verification.
Users can now request a reset link and set new password.
Closes #123
fix(api): prevent race condition in order processing
Add mutex lock to ensure orders are processed sequentially.
This fixes duplicate charge issues reported by users.
Fixes #456
refactor(cart): extract pricing logic to separate module
No functional changes. Improves testability and
separates concerns for future discount feature.
Execution
After analyzing staged changes, suggest a commit message.
Ask for confirmation before executing git commit -m "...".
$ARGUMENTS
Version History
- fa57065 Current 2026-07-25 10:17
