agentleFS
wado-langwado-lang/wado/.claude/skills/cr/SKILL.md

cr

Skill120 starsChanged 16 days agoMITView on GitHub

Check the branch marks its generated files, review it with /code-review at high, then answer the findings with /code-review-response.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check that the branch marks what it generates, so the review reads sources alone.

    line 8

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Code Review and Response

  1. Check that the branch marks what it generates, so the review reads sources alone. Among the files scripts/changed-sources.sh lists, find each one a script, a generator or a mise task writes. Mark it in .gitattributes (linguist-generated=true -diff) and in .coderabbit.yaml's path_filters, by a glob where its siblings are generated too. Then run mise run check-review-filters, which holds the two files to each other, and commit the marks.
  2. Invoke the code-review skill with high, over origin/main...HEAD: once the branch is pushed its upstream diff is empty, and a stale local main pulls in merged work.
  3. Answer its findings with the code-review-response skill. With no findings, invoke /distill alone: the response would have ended with it.

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.