What problem does it solve? Commit messages often become bloated with filler phrases, restated diffs, and AI attribution noise, making git history hard to scan. This Skill produces ultra-compressed, intent-preserving commit messages that follow the Conventional Commits specification. ## Core Features & Use Cases - Conventional Commits formatting: Enforces <type>(<scope>): <imperative summary> with types like feat, fix, refactor, perf, docs, test, chore, build, ci, style, and revert. - Strict length and style rules: Subject lines capped at 50 characters (72 hard limit), imperative mood, no trailing periods, and bodies wrapped at 72 characters only when the "why" is not obvious. - Auto-clarity for critical changes: Always includes a body for breaking changes, security fixes, data migrations, and reverts so future debugging retains context. - Use Case: After staging a breaking API rename, ask for a commit message and receive feat(api)!: rename /v1/orders to /v1/checkout with a BREAKING CHANGE footer and migration deadline, ready to paste. ## 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.
