Conventional commit
Prove whether a SKILL.md actually changes agent behavior (with/without) and which CLI harness does a task best — agent-native subagents or CLI. agentskills.io-compatible. Site: https://cskwork.github.io/skill-ab-eval/
npx -y skills add cskwork/skill-ab-eval --skill conventional-commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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
Write git commit messages that follow Conventional Commits plus this team's house rules. Use when writing or rewriting a commit message.
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.0 KB, as published. Nobody here has run it
Conventional Commit (house style)
Write every commit message exactly like this:
<type>(<scope>): <subject>
<body>
Refs: <TICKET-ID>
Rules:
- Type is one of:
feat,fix,docs,refactor,perf,test,chore. - Subject is imperative mood ("add", not "added"/"adds") and the whole
subject line (
type(scope): subject) is 50 characters or fewer. - Leave exactly one blank line between the subject and the body.
- Body explains the why, wrapped at 72 columns.
- Always end with a
Refs:footer citing the ticket ID. If a branch name or context contains an ID likePROJ-481, use it. Never omit this footer.
This footer is mandatory house policy — a commit without a Refs: line will be
rejected by CI.