Git Commit Formatter
This skill helps you generate semantic commit messages based on the Conventional Commits specification.
Usage
When the user asks to "commit changes" or "write a commit message":
- •Check Status: Run
git statusto see what is staged. - •Analyze Diffs: Run
git diff --cachedto see the actual changes. - •Generate Message: Formulate a commit message with the following structure:
code
<type>(<scope>): <description> [optional body] [optional footer(s)]
- •Types:
feat,fix,docs,style,refactor,perf,test,build,ci,chore,revert. - •Scope: A noun describing the section of the codebase (e.g.,
api,auth,parser).
- •Types:
- •Propose: Propose the command
git commit -m "..."to the user.
Rules
- •Keep the summary line under 72 characters.
- •Use the imperative mood in the subject line.
- •Mention closing issues in the footer (e.g.,
Closes #123).