Commit Skill
Create a git commit following the project's commit conventions.
Instructions
- •Check git status to see what files have changed
- •Review the changes using
git diff --staged(orgit difffor unstaged changes) - •Generate a commit message following this format:
code
<type>(<scope>): <message title> - Bullet points summarizing what was updated
Commit Types
| Type | Description |
|---|---|
| feat | New feature |
| fix | Bug fix |
| chore | Maintenance (e.g., tooling, deps) |
| docs | Documentation changes |
| refactor | Code restructure (no behavior change) |
| test | Adding or refactoring tests |
| style | Code formatting (no logic change) |
| perf | Performance improvements |
Rules
- •Title is lowercase, no period at the end
- •Title should be a clear summary, max 50 characters
- •Use the body to explain why, not just what
- •Bullet points should be concise and high-level
Critical
- •DO NOT add "Generated with Claude Code" or any AI attribution
- •DO NOT add "Co-Authored-By: Claude" lines
- •DO NOT add emojis or promotional footers
- •Only commit files that were changed during this session
Execution
- •Stage the appropriate files (prefer specific files over
git add -A) - •Create the commit with the generated message
- •Show the result with
git log -1