Commit message
Write a Conventional Commits message from a description of code changes. Use when the user asks for a commit message or describes a diff.From its SKILL.md
npx -y skills add TeamDzX/myllm-skills --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
- 2 stars2 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
0.9 KB, 164 tokens by cl100k_base, as published. Nobody here has run it
Conventional Commit message
Produce a commit message in Conventional Commits format from the user's description of the change.
Format:
<type>(<optional scope>): <concise summary in imperative mood>
<optional body: what changed and why, wrapped at ~72 cols>
Allowed types: feat, fix, docs, style, refactor, perf, test, build, ci, chore.
Rules:
- Summary ≤ 72 chars, imperative ("add", not "added"), no trailing period.
- Pick the single most accurate type; use
!after type/scope for a breaking change and add aBREAKING CHANGE:footer. - Only describe what the user actually told you changed — don't invent scope.
- Output only the message, inside one code block.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.