Index of every page on this site: llms.txt
All skills
scode avatar

/scode-commit-msg-reviewer

@03a9f7f
Run it yourself

Use only when the user explicitly invokes scode-commit-msg-reviewer by name, asks for commit messages to be checked by a fresh-context reader, or their standing instructions say to always use this skill. Do not trigger merely because a commit or PR is being created. Puts commit messages, PR titles/descriptions, and equivalent VCS prose in front of a cold reader who has not seen the change, and rewrites until that reader understands them; after the first signal, applies to all commit-message-like content for the rest of the conversation. Also use when the user says "scode-commit-msg-reviewer feedback: ..." to record feedback about how this skill performed.

  • 4 files
  • 21.9 KB
  • Updated 3 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/scode/dotfiles/scode-commit-msg-reviewer

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

feedback.md

≈340 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Feedback capture

The user gave feedback about how this skill performed. Pause whatever you are doing and record it as described here before resuming. The record exists so the skill's author can hand it to an agent working in the skill's source repository and ask for improvements — write it for that reader, who has no access to this session.

Append (never overwrite) a markdown entry to $XDG_STATE_HOME/scode-commit-msg-reviewer/feedback.md, defaulting to ~/.local/state/scode-commit-msg-reviewer/feedback.md when XDG_STATE_HOME is unset. Create the directory if needed. Each entry contains:

  • A ## <date> — <short title> heading.
  • The user's feedback, verbatim or near-verbatim.
  • What actually happened: the candidate message(s), what the reviewer said each round, and what you did with it.
  • Root-cause analysis: which instruction in SKILL.md or reviewer.md allowed the bad outcome, or what missing instruction would have prevented it. Mark speculation as such.
  • A concrete suggested change — exact replacement wording or a literal diff against the file it targets — always accompanied by the problem it fixes and the intent behind the change, so the improving agent can adapt it rather than apply it blindly.

After writing, show the user the entry (or a faithful summary of it) and tell them which file you appended to.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 03a9f7f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 months ago

README badge

README badge for scode/dotfiles/scode-commit-msg-reviewer