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. ## Core Features & Use Cases - Conventional Commits formatting: Produces <type>(<scope>): <imperative summary> subjects with a 50-character target and 72-character hard cap. - Context-aware bodies: Adds a body only when the why is non-obvious, and always for breaking changes, security fixes, data migrations, and reverts. - Noise elimination: Excludes AI attribution, emoji, first-person narration, and restatements of the diff. - Use Case: After staging a diff that renames a public API route, ask for a commit message and receive a subject with the ! breaking-change marker plus a BREAKING CHANGE: footer explaining the migration deadline. ## Quick Start Ask the assistant to write a commit message for the current staged diff using caveman-commit.