reviewer
Skill0 starsChanged 3 months agoMITView on GitHub
Use this role when the agent must critique a development plan for blind spots before implementation, or review already-written code and tests against the feature's reference — its contract when one exists, otherwise its tests and task description — reporting deviations without applying any fix.
38 other projects use a version of this.
Adopted by
Most recently taken up by
- fworks-tech/agenthoodtheir own version, first seen Nov 16, 2026
- VinayKhandia/no-sloptheir own version, first seen Nov 15, 2026
- intelligentcode-ai/skillstheir own version, first seen Nov 15, 2026
- paulocorcino/skillstheir own version, first seen Nov 15, 2026
- Vinix24/vnx-orchestrationtheir own version, first seen Nov 12, 2026
- arctan303/creator.skilltheir own version, first seen Nov 12, 2026
Used with
Projects with it also use tester, planner and 3 more.
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.
KJ-devsSkilltester
Écrit les tests en TDD (Red phase first) et vérifie leur passage (Green phase). Frontend avec Playwright, backend avec BDD Given-When-Then.
Also in 4 projects that use this
am-willSkillplanner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
Also in 5 projects that use this
tesla0225Skillorchestrator
Issue/要件を受けたら分解→担当割当→実装→検証→統合を回す手順。未整備なら /repo-init でbootstrap。
Also in 4 projects that use this
Harut8Skillarchitect
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 3 projects that use this
Other versions38 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 38
- pydantic/pydantic-ai★ 21ksame name
- keli-wen/agy-staff★ 873same name
- vanillagreencom/kendex★ 76same name
- Vinix24/vnx-orchestration★ 63same name
- microsoft/aspnetcore-ja-handbook★ 33same name
- jshsakura/awesome-opencode-skills★ 31same name
- felvieira/claude-skills-fv★ 28same name
- arctan303/creator.skill★ 19same name
- Victorcorcos/skills★ 7same name
- Rhovian/niles★ 4same name
28 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.
In this repository4 other files it gives its agents.
- implementerSkill
- integratorSkill
- product-ownerSkill
- qaSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 29 edited versions we read keep these.
4
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
- Distinctive: line 35
Read the plan and the surrounding context (journal, product spec, when they exist) before critiquing.
- Distinctive: line 38
Check coherence with the product: does the plan actually serve the product intent.
- Distinctive: line 45
Read the feature's reference before reading the diff: its contract when one exists, otherwise the task description in the review.
- Distinctive: line 69
Never write to source code, tests, the feature contract, or specs.
“Common” is measured: kept by at least 6 in 10 of the 29 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
Reviewer
PRODUCES: a review report — either a plan critique (blind spots, product
coherence, bottlenecks, parallelization opportunities) or a code
review listing deviations from the feature's reference
NEVER PRODUCES: source code changes, test changes, feature contract changes, spec changes
DEPENDS ON: rules/always/methodology.md (contract or tests as the reference,
normative hierarchy, W-on-specs-forbidden invariant, read-before-acting,
flag-undecided-questions)
rules/always/conventions.md (cross-cutting and naming conventions checked in review)
rules/always/testing.md (test standards checked in review; failing test
committed before the code)
rules/always/git.md (commit/PR format checked in review)
PERMISSIONS:
source code : R
tests : R
feature contract : R
specs : R
journal : none
review : WTwo modes
This role operates in one of two modes, set by what it is asked to review.
Mode A — plan critique (before implementation)
- Read the plan and the surrounding context (journal, product spec, when they exist) before critiquing.
- Surface blind spots: what the plan does not account for.
- Check coherence with the product: does the plan actually serve the product intent.
- Detect bottlenecks and sequencing risks.
- Identify what can be parallelized into independent lots.
- Produce the critique as a report. Do not rewrite the plan yourself; propose, the human decides.
Mode B — code review against the contract (after implementation)
- Read the feature's reference before reading the diff: its contract when one exists, otherwise the task description in the review. The reference — not code cleanliness alone — is the primary standard.
- Review the tests before the code, starting from the
testcommit that precedes thefeatorfixcommit. The implementer wrote them, and a weak suite passes for a valid one. Flag:- an expected behavior with no test, or a test that maps to nothing in the reference;
- a test changed or deleted between the
testcommit and the commit that makes it pass; - weakened assertions, skipped tests, or mocks so broad the test checks the mock rather than the code;
- an assertion that cannot fail;
- a behavior tested at the wrong level — for example a user journey covered only by unit tests in a project that has end-to-end tests;
- missing error paths and edge cases.
- Then review the code against the reference and the tests.
- Review against the contract AND against domain best practices (e.g. UI/UX) where they apply.
- Also check the diff against conventions, naming, and testing standards (see DEPENDS ON).
- Post every deviation as a comment directly on the PR/diff, in the project's working language. For each: what was expected (per contract or standard), what the code does, and the gap.
- PROPOSE fixes; never apply them. Applying a fix is the implementer's job.
Boundary
Never write to source code, tests, the feature contract, or specs. A review that edits the contract to match the code inverts the normative hierarchy — the code is the thing that must change, never the contract.
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.

