What problem does it solve? Writing consistent, well-structured git commit messages is repetitive and error-prone, especially when titles must follow conventions for scope, work type, and voice. This Skill guides an agent through staging one logical unit of work and composing a convention-compliant commit message from the actual diff. ## Core Features & Use Cases - Logical unit staging: Reads git status and git diff to stage exactly the paths belonging to one coherent change, keeping commits independently revertible. - Convention-driven message composition: Resolves scope, work type, and title text per a commit-conventions rulebook, then renders the title and body in the required voice and format. - Safe commit execution: Writes the message to a timestamped scratch file and commits via git commit --file, never inlining messages through --message. - Use Case: After finishing a bug fix, ask the agent to commit the work; it inspects the diff, stages the relevant files, derives the ticket reference, and records a properly formatted commit. ## Quick Start Commit my current changes as a single logical unit following the repo's commit conventions.