Menu
Commit message conventions and format. Use when creating git commits or reviewing commit messages.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | commit-style |
| description | Commit message conventions and format. Use when creating git commits or reviewing commit messages. |
| disable-model-invocation | true |
Single line. Imperative mood. Aim for 50 characters, max 72. State WHAT changed, not WHY or HOW.
Project format varies. Check before committing:
git log --oneline -10 for recent patternsCommon patterns:
feat: Add feature (conventional commits)Add feature (plain verb)GOOD:
Add dark mode toggleFix lightbox navigationExtract shared logicBAD:
Add dark mode toggle component to settings...Added support for dark modeRefactored for better maintainabilityDiffs tell the story. Commit message states the change. History is scannable. Long messages hide the change.