What problem does it solve? Writing consistent, well-structured commit messages is tedious and often skipped, leading to unreadable git history. This Skill inspects your staged changes, drafts a Conventional Commits message, and commits only after you approve it. ## Core Features & Use Cases - Diff-Based Message Drafting: Reads git diff --cached to derive an accurate subject and body describing what actually changed. - Conventional Commits Formatting: Enforces type prefixes (feat, fix, refactor, docs, test, chore, move), optional scopes, 72-character limits, and imperative mood. - Mandatory Confirmation Flow: Presents the proposed message with Approve, Edit in chat, Edit in editor, or Cancel options before any commit runs. - Use Case: After staging a refactoring across several modules, ask for a commit and receive a message like refactor(core): extract layout engine into standalone module with a bulleted body, ready to approve or edit. ## Quick Start Ask the assistant to commit my staged changes with a proper commit message.