Commit message
Skill kin0992/dev-toolkit/packages/skills/src/git/commit-message
Platform Engineering toolkit: reusable GitHub Actions, AI Skills, and shared TypeScript configs.
npx -y skills add kin0992/dev-toolkit --skill commit-messageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
**UTILITY SKILL** - Generate a classic Git commit message from a staged diff. USE FOR: write commit message, generate commit message from diff, summarize staged changes, create commit text, compose git commit. DO NOT USE FOR: generating PR descriptions (use pr-title-description), writing changelog entries, conventional commits format. INVOKES: git diff --staged for reading staged changes. FOR SINGLE OPERATIONS: Use git commit -m directly for trivial one-liners.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.7 KB, as published. Nobody here has run it
Generate a classic Git commit message
Turn a staged diff into a classic Git commit message. Conventional Commits are forbidden.
Instructions
- Read the entire diff; identify the primary intent of the change.
- Write a subject line: ≤50 chars, capital start, no period,
imperative mood, no Conventional Commits prefix (
feat:,fix:…). - Prefer specific verbs ("Fix", "Add", "Remove", "Rename", "Refactor"). Avoid vague verbs like "Update".
- Add a body only when it adds useful context. Separate with a blank line, wrap at 72 chars, explain what and why.
- If the change touches unrelated areas, suggest splitting into multiple commits.
- Never invent issue numbers.
Output
Return only the commit message text, no commentary or fences. If a body is needed:
<subject line>
<body>
Example
Guard startup when config is missing
Prevent the app from crashing when optional configuration is absent.
This keeps startup behavior predictable and makes the fallback path
explicit.
Common edge cases
- Small, self-explanatory changes need only a subject line.
- If the diff mixes unrelated changes, recommend splitting into separate commits.