What problem does it solve? Writing commit messages that both summarize what shipped and preserve the reasoning behind a change is tedious and often skipped, leaving history that is hard to scan or reconstruct later. ## Core Features & Use Cases - Staged-change analysis: Reads git status and the staged diff to understand exactly what is being committed. - Convention matching: Follows the project's commit format from .agents/config/conventions.md, or infers prefixes, trailers, and casing from recent git history. - Structured message shape: Opens with a plain-language summary of what shipped, then compresses the why into a body under roughly 150 words. - Approval gate: Shows a summary and proposed message, then waits for confirmation — it never auto-commits. - Use Case: After staging a refactor, invoke the skill to get a commit message that leads with what changed and records the motivation a future reader could not recover from the diff. ## Quick Start Analyze my staged changes and propose a commit message following this project's conventions, then wait for my approval before committing.
