Cavemenko commit
Generate short commit messages in Conventional Commits format. Use when user asks to generate commit, describe changes for git, or calls /cavemenko-commit.From its SKILL.md
npx -y skills add ruslanlap/cavemenko --skill cavemenko-commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 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.
SKILL.md
1.3 KB, as published. Nobody here has run it
Generate short commit msg for current staged changes.
Format
Conventional Commits. Structure: <type>(<scope>): <description>
Types: feat, fix, docs, style, refactor, perf, test, chore, build, ci
Rules
- Subject: ≤50 chars, imperative, lowercase after type
- No period at end of subject
- Body: only when "why" is not obvious from subject
- Explain why, not what —
git diffalready shows what - Empty line between subject and body
- Body: wrap at 72 chars
Examples
Good:
fix(auth): check token expiry with strict inequality
Previous check used `<=` which accepted tokens at exact expiry time.
Clock skew between services caused intermittent 401s.
Good (self-sufficient subject):
docs: fix typo in README install instructions
Bad:
Updated some files.
Bad (repeating what diff shows):
feat: add new function called validateInput to utils.js
Process
- Read
git diff --cached - Determine type and scope
- Write subject (≤50 chars, imperative)
- Decide if body needed — only if "why" not obvious
- Output ready message in one block, no explanations