What problem does it solve? Messy commit histories with vague messages like "wip" or "fix stuff" make code reviews painful, break git bisect, and hide the reasoning behind changes. This Skill enforces Conventional Commit prefixes, single-purpose commits, and the rule that every commit compiles independently. ## Core Features & Use Cases - Standard Prefix Taxonomy: Applies feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert prefixes with a decision tree for choosing the right one. - Commit Sequencing & Hygiene: Plans logical commit order, stages changes incrementally, verifies each commit compiles, and cleans up history with interactive rebase before review. - Enforcement Tooling: Provides a commit-msg git hook script that rejects messages without a valid prefix, plus a squash-vs-preserve policy for pull requests. - Use Case: When preparing a feature branch for review, split bundled changes into focused commits (feature, tests, docs), reword vague messages, and squash typo fixes so reviewers see a clean, bisectable history. ## Quick Start Apply the git-commit-conventions skill to split my current uncommitted changes into properly prefixed, independently compiling commits.
