What problem does it solve? Writing consistent, well-scoped Git commit messages is error-prone: unrelated changes get bundled in, message style drifts from project conventions, and commits happen before the user has reviewed the final wording. This Skill enforces a disciplined commit workflow that inspects the actual change set, matches repository style, and requires explicit confirmation before committing. ## Core Features & Use Cases - Change-set scoping: Inspects git status and staged diffs to determine exactly what "commit this" refers to, staging only the intended changes and refusing to bundle unrelated work. - Style-matched message drafting: Reads recent commit history to infer tense, capitalization, and prefix conventions like fix: or feat:, then drafts a subject-first message with no filler or emojis. - Confirmation-gated commits: Previews the final message in chat and asks for explicit confirmation before running git commit, then reads back the finished commit and only pushes with authorization. - Use Case: After finishing a bug fix, you say "commit this" and the Skill stages only your fix, drafts a message matching the repo's conventional-commit style, shows it for approval, and commits once you confirm. ## Quick Start Ask the assistant to commit the current changes, for example by saying "commit this", and it will stage the relevant changes, draft a message, and wait for your confirmation.