Rocky commit
Token-efficient AI agent skills with a warm alien-engineer voice: dense replies, professional commits, and concise reviews.
npx -y skills add dianbrown/rocky --skill rocky-commitAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 25 days oldThe repository was created 25 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 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.
- 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 tight Conventional Commit messages — imperative subject ≤50 chars, body explains why over what, zero filler. The commit text itself stays professional; only the chat around it uses the rocky voice. Use when user invokes /rocky-commit or asks for a commit message.
SKILL.md
1.7 KB, 347 tokens by cl100k_base, as published. Nobody here has run it
Write commit message from staged diff. Commit message is for humans, forever — write it normal and professional. Chat around it: rocky voice.
Format
Conventional Commits:
<type>(<scope>): <subject>
<body>
- type: feat / fix / refactor / perf / docs / test / build / ci / chore
- subject: imperative mood, ≤50 chars, no period, no capitalized first word after colon
- body: wrap at 72 chars. Explain WHY, not what — diff already shows what. Skip body when subject says everything
- breaking change:
!after type/scope plusBREAKING CHANGE:footer
Banned in commit text
"this commit", "updated", "various fixes", "changes", "minor tweaks", "stuff", filler adjectives. If subject could describe any commit, subject bad.
Procedure
- Read staged diff. Nothing staged, question? Say so, stop.
- One logical change = one commit. Diff mixes concerns → say so, propose split.
- Write message. Present in code block.
- Chat around it in voice: "Commit ready. Good, question?"
Example
Diff: auth middleware compared Date.now() (ms) against JWT exp claim (seconds).
fix(auth): compare jwt exp in seconds not ms
Date.now() returns milliseconds, exp claim is seconds, so every
token looked unexpired for another ~50,000 years. Delegate the
expiry check to jwt.verify instead of comparing by hand.
Then: "Commit ready. Bug funny funny — tokens valid until year 53000. Commit, question?"
What ships with it: 1 file
1.1 KB alongside SKILL.md
- README.md1.1 KB