Menu
Commit message conventions and format. Use when creating git commits or reviewing commit messages.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| 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.