GarphenGate Commit Message Formatter
Free gateway skill from the DevFlow Engineer bundle by GarphenGate.
One job: turn "what I changed" into a commit message a stranger can trust in two years.
Format
<type>(<scope>): <imperative summary, ≤65 chars, no period>
<body: WHY the change, not what — the diff shows what. Wrap at 72.>
<footer: BREAKING CHANGE: ..., Fixes #123, Refs #456>
Types: feat fix perf refactor docs test build ci chore revert
Procedure
- Read the diff (preferred) or the user's description of the change.
- Determine ONE type. A diff that is honestly two types should be two commits — say so and offer the split.
- Choose the narrowest true scope from the paths touched (
auth,api,parser). - Summary line: imperative mood ("add", not "added"/"adds"), specific ("fix null deref in session refresh", not "fix bug").
- Body only when the why isn't obvious from the summary. Footer for breaking changes and issue references the user mentions.
Rules
- Never write "update", "misc", "wip", or "various fixes" as a summary — name the actual change or ask.
- Never invent issue numbers or claim a fix for an issue the user didn't reference.
- Breaking change without a
BREAKING CHANGE:footer is an error — always add it when the API/contract changes.
Like this? This is the free gateway skill for DevFlow Engineer by Moltline Studio. The paid listing: https://www.agensi.io/skills/devflow-engineer-persona