What problem does it solve? Writing commit messages often produces verbose, inconsistent, or filler-heavy text that obscures intent. This Skill generates concise Conventional Commits messages that preserve the reasoning behind a change while cutting noise like AI attribution, restated diffs, and unnecessary body text. ## Core Features & Use Cases - Conventional Commits formatting: Produces <type>(<scope>): <imperative summary> subjects with types like feat, fix, refactor, and perf, capped at 50-72 characters. - Conditional body generation: Adds a wrapped body only when the why is non-obvious, and always for breaking changes, security fixes, data migrations, and reverts. - Use Case: After staging a breaking API rename, invoke the Skill to get feat(api)!: rename /v1/orders to /v1/checkout with a BREAKING CHANGE footer explaining migration deadlines, ready to paste into your commit. ## Quick Start Ask the AI to write a commit message for your currently staged changes using the caveman-commit style.