What problem does it solve? Writing clear, consistent commit messages is tedious and often results in vague entries like "update" or "fix stuff". This Skill analyzes your staged git changes and drafts a well-structured conventional commit message, without staging or committing anything itself. ## Core Features & Use Cases - Diff-Based Message Generation: Reads git diff --staged and drafts a message specific to the actual changes, using conventional types like feat, fix, refactor, docs, test, chore, perf, and ci. - Style Enforcement: Applies commit message guidelines including imperative mood, summaries under 50 characters, no trailing period, and bodies that explain why rather than what. - Breaking Change Marking: Formats breaking changes with the type! prefix and a BREAKING CHANGE footer including migration notes. - Use Case: You staged a retry-with-backoff fix in fetch.py. Ask for a commit message and get something like "fix: add retry with backoff to get_price" with a body explaining the flaky HTTP call. ## Quick Start Use git-commit-helper to write the commit message for the changes I have staged.
