What problem does it solve? Writing consistent, meaningful commit messages is a common friction point: subjects run too long, bodies restate the diff, and unrelated changes get batched into one commit. This Skill produces terse, standards-compliant commit messages and PR titles that pass automated commit-msg hook validation. ## Core Features & Use Cases - Conventional Commits Generation: Produces type(scope): imperative summary subjects under 50 characters with the correct type vocabulary (feat, fix, refactor, perf, docs, test, chore, build, ci, style, revert). - WHY-Focused Bodies: Writes body text explaining motivation and consequences rather than listing changed files, required for multi-file commits, breaking changes, security fixes, migrations, and reverts. - Micro-Commit Discipline: Enforces one logical change per commit, never batching implementation with tests or docs with code. - Use Case: After staging a fix that guards empty log handles, ask for a commit message and receive a compliant subject plus a body explaining the spurious escalation the guard prevents, ready to paste and pass the commit-msg.sh hook check. ## Quick Start Ask the assistant to write a commit message for your staged changes using the commit-discipline rules.
