agentleFS
rafapeixerrafapeixer/go-skills/.claude/skills/review-skill/SKILL.md

review-skill

Skill1 starsChanged 31 days agoMITView on GitHub

Review one go-skills skill against the repository rules and current Go facts. Use before opening a PR for a new or changed skill.

21 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Position and reasons: Every rule is imperative, one sentence, and the "Why" section says what breaks without it.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review skill

Review skills/$ARGUMENTS/ against CLAUDE.md. Report findings as a list, most severe first; do not edit unless asked.

Check:

  1. Format. bash scripts/validate.sh and bash scripts/test-examples.sh pass.
  2. One decision. The skill covers a single decision; if it covers two, say where to split.
  3. Position and reasons. Every rule is imperative, one sentence, and the "Why" section says what breaks without it. Flag any "it depends" that does not say on what.
  4. Facts are current. Every API, version and default named in the skill exists and behaves as described in the Go release that the examples' go directive targets. Rules that need a newer release carry an inline version gate. Verify doubtful claims against go.dev release notes and pkg.go.dev.
  5. Examples. The good example is the smallest code that shows the rules. The bad example contains mistakes people actually make, each marked // MISTAKE:. The inline excerpts match the files.
  6. Checklist. 5 to 10 yes/no items that a reviewer can answer by reading code.
  7. Exceptions. "When not to apply" lists real cases and what to do instead.
  8. Defaults. The skill does not tell readers to switch off a good default (post-quantum TLS curves, container-aware GOMAXPROCS, pgx extended protocol) without a stated reason.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.