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 subjects in <type>(<scope>): <imperative summary> form with types like feat, fix, refactor, and revert, capped at 50-72 characters. - Selective 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, ask for a commit message and receive feat(api)!: rename /v1/orders to /v1/checkout with a BREAKING CHANGE footer explaining the migration deadline. ## Quick Start Ask the assistant to write a commit message for your staged changes and it will output a ready-to-paste Conventional Commits message.