agent-review
Skill4 starsChanged 15 days agoMITView on GitHub
Run a peer CLI agent (Claude Code, Codex, OpenCode, pi), or prepare a reviewer handoff via user relay, to review code, diffs, or plans, including a plan through its implementation and commits, when explicitly requested by the user or via $agent-review.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- facebookresearch/autoform-bottheir own version, first seen Nov 12, 2026
- blamechris/chroxytheir own version, first seen Nov 8, 2026
- khoralabs/skillstheir own version, first seen Nov 1, 2026
- mementomori-co/maker-masterytheir own version, first seen Oct 25, 2026
- alexaiarchitect/google-adk-skillstheir own version, first seen Oct 20, 2026
- fabioc-aloha/Alex_ACT_Editiontheir own version, first seen Oct 13, 2026
Used with
Projects with it also use commit.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- DmNote-App/DmNote★ 4.2ksame name
- foldkit/foldkit★ 1.1ksame name
- Tsuzat/Edra★ 675same name
- facebookresearch/autoform-bot★ 143same name
- blamechris/chroxy★ 8same name
- ethanaubuchon/dossier-tradecraft★ 3same name
- mementomori-co/maker-mastery★ 2same name
- khoralabs/skills★ 1same name
- ngc-shj/claude-code-config★ 1same name
- alexaiarchitect/google-adk-skills★ 0same name
1 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
9
Distinctive
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
- Distinctive: line 8
Use a peer agent as a reviewer, not as the authority.
- Distinctive: line 9
Keep responsibility for deciding which feedback to accept, reject, or discuss.
- Distinctive: line 16
If the user explicitly requests user relay, read Review via user relay and Review loop.
- Distinctive: line 20
If neither user relay nor a CLI reviewer is named, or the choice is ambiguous, ask the user instead of guessing.
- Distinctive: line 37
When running the CLI path, also read the document matching the host environment:
- Distinctive: line 42
If no host document exists, run the helper in the foreground with the required permissions.
- Distinctive: line 48
If multiple targets are plausible or the request is underspecified, ask what to review.
- Distinctive: line 51
If the subject is a plan that you will implement yourself, also follow Plan and implementation.
- Very specific: line 56
Use path-based input for project files that the reviewer can access.
- Distinctive: line 61
If the user asks for feedback on this skill or on how a review went, rather than on the reviewed artifact, also read Meta-review.
“Common” is measured: kept by at least 6 in 10 of the 9 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.
Files
Agent Review
Use a peer agent as a reviewer, not as the authority. Keep responsibility for deciding which feedback to accept, reject, or discuss.
Choose the runtime branch
Act as the host agent running the skill. The external reviewer follows the generated review prompt and does not read this skill.
- If the user explicitly requests user relay, read Review via user relay and Review loop.
- Otherwise, read Review via CLI, Review loop, and any matching host and reviewer guidance selected below.
Load only the common documents for the selected review path and its applicable host and reviewer documents. If neither user relay nor a CLI reviewer is named, or the choice is ambiguous, ask the user instead of guessing.
CLI reviewers
Available review agents, by their --agent identifier:
claude(Claude Code).codex(Codex).opencode(OpenCode) — read OpenCode reviewer guidance.pi(pi) — read pi reviewer guidance.
Map a naturally named reviewer to the identifier on the left.
Pass the selected identifier, or manual, through the required --agent flag on every round.
CLI review requires Node.js 22.18 or newer, npm, first-run network access, the selected reviewer's CLI on PATH, and its authentication in the normal local environment.
Select host guidance
When running the CLI path, also read the document matching the host environment:
- Claude Code host: read Claude Code host guidance.
- Codex host: read Codex host guidance.
If no host document exists, run the helper in the foreground with the required permissions.
Identify the review subject
Review only a clearly identified subject from context, such as a diff, plan, design note, issue summary, code snippet, or project files. In Plan Mode, use the current plan text as the subject. If multiple targets are plausible or the request is underspecified, ask what to review.
State the subject and compose the review focus according to Review focus. If the subject is a plan that you will implement yourself, also follow Plan and implementation.
For repository changes reviewed via CLI, instruct the reviewer to run the exact diff command rather than pasting a captured diff.
For a working-tree review, also instruct the reviewer to run git status --short and inspect every in-scope untracked file.
Use path-based input for project files that the reviewer can access.
Materialize larger non-repository subjects in /tmp only when the selected review path can access that file.
Meta-review
If the user asks for feedback on this skill or on how a review went, rather than on the reviewed artifact, also read Meta-review.
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
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.

