agentleFS
Sign inStart free
gregwebsgregwebs/skills-sdlc/skills/code-review-with-followup/SKILL.md

code-review-with-followup

Skill20 starsChanged 44 days agoMITView on GitHub

Adversarial code review with explicit followup instructions

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Use the /orchestration skill to manage sub-agents.

    line 6
  2. Distinctive:

    If there are no findings in review (rare unless the changes is trivial), code review is complete.

    line 13
  3. Very specific:

    Ask the coder to make changes and provide an explanation for them as code-review-followup.md

    line 17

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Use the /orchestration skill to manage sub-agents.

Delegate review to a reviewer sub-agent. Use planner as an alternate.

A reviewer performs a /code-review-adversarial using instructions supplied to this skill. Persist its ouput as code-review.md.

If there are no findings in review (rare unless the changes is trivial), code review is complete. Otherwise, perform a followup review.

Give a coder (alternate implementer) sub-agent code-review.md along with what was reviewed. Ask the coder to make changes and provide an explanation for them as code-review-followup.md

Perform a followup review of how concerns in code-review.md were addressed by code-review-followup.md and a diff of the followup changes. Have the coder address any further followup changes needed.

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.

Check your setup, free