What problem does it solve? Writing inconsistent or vague git commit messages makes project history hard to read, breaks automated changelog generation, and slows down code review. This Skill enforces the Conventional Commits specification so every commit message follows a structured, machine-parseable format. ## Core Features & Use Cases - Structured Message Generation: Builds commit messages with type, scope, description, body, and footer fields using a defined XML template. - Guided Git Workflow: Walks through git status, git diff, staging, and committing so changes are reviewed before the message is written. - Validation Rules: Enforces allowed types (feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert), imperative mood descriptions, and BREAKING CHANGE footers. - Use Case: After modifying several files in a feature branch, run the workflow to inspect the diff, then produce a message like "feat(parser): add ability to parse arrays" and commit it directly in the terminal. ## Quick Start Ask the assistant to review your staged git changes and generate a conventional commit message, then commit them.