What problem does it solve? Commit messages often become bloated with filler phrases, redundant context, and inconsistent formatting, making git history hard to scan and debug. This Skill produces ultra-compressed, intent-preserving commit messages that follow the Conventional Commits specification. ## Core Features & Use Cases - Conventional Commits Enforcement: Generates subjects in <type>(<scope>): <imperative summary> format with types like feat, fix, refactor, and perf, capped at 50-72 characters. - Noise Elimination: Strips filler such as "This commit does X", AI attribution, emoji, and first-person language while preserving the reasoning behind changes. - Contextual Body Rules: Adds a body only for non-obvious rationale, breaking changes, security fixes, migrations, and issue references like Closes #42. - Use Case: After staging a breaking API rename, ask for a commit message and receive a subject with the ! breaking-change marker plus a migration-note body ready to paste. ## Quick Start Ask the assistant to write a commit message for your staged changes using the caveman-commit style.