Defines how to write and format git commit messages. Use this skill whenever the user asks you to write, draft, suggest, or format a git commit message, summarize changes into a commit, or help stage and describe code changes. Trigger even for casual requests like "write me a commit for this" or "what should my commit say".
Defines how to write and format git commit messages. Use this skill whenever the user asks you to write, draft, suggest, or format a git commit message, summarize changes into a commit, or help stage and describe code changes. Trigger even for casual requests like "write me a commit for this" or "what should my commit say".
Use the imperative mood: "Add feature" not "Added feature" or "Adds feature"
No trailing period
Describe what the commit does, not how
Blank line
Always one blank line between the summary and the bullet list
Never omit this blank line
Bullet points
Each bullet describes a single, specific change
Short and crisp -- one line per bullet
Start each bullet with a verb in the imperative mood (Add, Fix, Remove, Update, Rename, Move, Extract, etc.)
No trailing periods
No fluff or filler words
Never include
Co-author lines (no Co-authored-by: trailer)
Generated by Claude or any AI attribution
Redundant context already obvious from the diff
Examples
Good:
Add user authentication middleware
- Add JWT validation to protected routes
- Return 401 on missing or expired token
- Extract auth logic into separate middleware file
- Add unit tests for token validation
Fix null pointer crash on empty cart checkout
- Guard against null items array before totalling
- Add early return when cart has no items
- Log warning when checkout attempted on empty cart
Bad (do not do this):
Updated some stuff and fixed a few things that were broken and also added
some new features to the codebase
- I made some changes to the auth file because it was crashing
- Also fixed the cart thing
- Co-authored-by: Claude <noreply@anthropic.com>
