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, keeping repository history readable and debuggable. ## Core Features & Use Cases - Conventional Commits formatting: Produces <type>(<scope>): <imperative summary> subjects with types like feat, fix, refactor, and revert, capped at 50-72 characters. - Why-over-what bodies: Adds a body only when the reasoning 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, while supporting issue references like Closes #42. - Use Case: After staging a breaking API rename, invoke the Skill to receive a ready-to-paste message with a ! marker and a BREAKING CHANGE: footer explaining the migration deadline. ## Quick Start Ask the assistant to write a commit message for your staged changes, or invoke /caveman-commit, and paste the returned code block into your git commit.
