Commit msg
Skill NSBen/skillfoundry/src/skillfoundry/data/starter_skills/commit-msg
Use when you have staged changes and need a clear, conventional-commits style message that explains the why, not just the what.From its SKILL.md
npx -y skills add NSBen/skillfoundry --skill commit-msgAssembled 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 file declares
Copied from the file, not written here
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.1 KB, 181 tokens by cl100k_base, as published. Nobody here has run it
Commit Message
When to use
Invoke this skill after git add and before git commit to draft a high-quality message.
Steps
- Read the staged diff (
git diff --cached) and any linked issue. - Pick a type: feat, fix, docs, refactor, test, chore, perf, ci.
- Write a subject under 72 chars:
<type>(<scope>): <imperative summary>. - Add a body only when the why is non-obvious: what changed and why.
- Reference the issue id when one exists.
Examples
- "Write a commit message for my staged changes"
- "Summarize this diff as a conventional commit"
References
Use the imperative mood ("add" not "added"); never include noise like "update code" or file lists the diff already shows.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.