review
Skill1 starsChanged 4 days agoMITView on GitHub
Review code before it merges, or audit a whole codebase - correctness, security, data safety, performance, tests, duplication and architecture - and report findings with a concrete failing case and the smallest fix. Use when asked to review a diff, PR, branch or file, audit a repo, check code an agent wrote, or at the end of a milestone.
192 other projects use a version of this.
Adopted by
Most recently taken up by
- dzhng/skillstheir own version, first seen Nov 15, 2026
- muxy-app/muxytheir own version, first seen Nov 15, 2026
- macro-inc/macrotheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- markmhendrickson/neotomatheir own version, first seen Nov 15, 2026
- felipeam86/pipe-skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use close-spec, design-with-images and 10 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.
dzhngSkillclose-spec
When a spec under specs/<feature>/ is done shipping (a write-spec build, or any planned task that produced a spec), archive it to specs/done/ and rewrite it from a build-plan into a durable rationale — the why, the principles, the invariants — pointing back to the real code for the how. Use when implementation has landed and the plan no longer matches what shipped, or the user says a feature/spec is finished. Pairs with [write-spec](../write-spec/SKILL.md) (the plan this closes) and [review](../review/SKILL.md) (run before closing).
Also in 5 projects that use this
dzhngSkilldesign-with-images
Explore UI and visual design with image generation, then iterate the real implementation against the user-selected concept. Use when brainstorming visual directions, offering mockup variants, or implementing an approved generated design; do not stop at the mockups or the first code approximation.
Also in 5 projects that use this
LambenthanSkilldaily-arxiv
每日从 arXiv 拉取新论文,过滤相关性,auto-ingest 高优先级论文,检测 SOTA 更新
Also in 5 projects that use this
LambenthanSkillexp-eval
实验判决门:Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges
Also in 5 projects that use this
- +3 more from dzhng
- +5 more from Lambenthan
Other versions192 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 192
- garrytan/gstack★ 142ksame name
- ansible/ansible★ 71ksame name
- docling-project/docling★ 71ksame name
- traefik/traefik★ 66ksame name
- ClickHouse/ClickHouse★ 51ksame name
- temporalio/temporal★ 24ksame name
- ccch1mneyyy/dsh-Go★ 24ksame name
- tisfeng/Easydict★ 15ksame name
- juicedata/juicefs★ 15ksame name
- elie222/inbox-zero★ 13ksame name
182 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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agents-mdSkill
- app-iconSkill
- buildSkill
- cloneSkill
- debugSkill
- design-systemSkill
- docker-optimizeSkill
- improve-loopSkill
- mac-appSkill
- mac-designSkill
- product-briefSkill
- quality-barSkill
- refactorSkill
- researchSkill
- start-hereSkill
- stop-overthinkingSkill
- ui-directorSkill
- user-storiesSkill
- ux-designSkill
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 157 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 28
Scale: check-then-write races, a query per item, lists or memory that only grow, work repeated by every process, O(n²) on real input.
- Distinctive: line 42
Every finding has a concrete case: "this input or situation leads to this wrong result".
- Distinctive: line 44
Before calling code unused or duplicated, grep the whole tree, including tests, config and dynamic references.
- Distinctive: line 64
Every changed line was read, every finding has a case and a fix, and the report says what was not checked.
“Common” is measured: kept by at least 6 in 10 of the 157 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
Review
The outcome: the code that merges is correct, safe and part of one coherent system, and every finding comes with proof. A review that lists taste and vague worries teaches nothing.
1. Map first
- What is it supposed to do? Read the story, the brief or the PR description, then the diff.
- For an audit: the README, entry points, config, tests, and the expected load (one person or many users and processes at once). Go deep where a mistake costs the most (input, money, auth, data writes, background jobs), and say which parts you did not read.
- Trace the main flows end to end: where data comes in, what is stored, what goes out.
2. Look for, in this order
- Correctness: wrong results, crashes, missed edge cases (empty, zero, last item, rounding, time zones, concurrent edits), callers that disagree with what a function returns, the same rule applied differently in two places, acceptance criteria not met.
- Security: unvalidated input at trust boundaries, injection, broken auth or access checks, secrets in code or logs, unsafe defaults, data exposed to the wrong user, risky dependencies.
- Data safety: swallowed errors, writes in the wrong order, missing transactions, migrations that lose data, no way to undo a destructive action.
- Scale: check-then-write races, a query per item, lists or memory that only grow, work repeated by every process, O(n²) on real input. Judge against the expected load.
- Tests: risky logic with no test that fails when it breaks; tests that pass without testing anything; skipped or loosened tests.
- One system: a second version of a helper or component that already exists, near-copies that must change together, a rule that lives in two places, an abstraction with one user, code that ignores the project's conventions, tokens or design system.
- Architecture: a module doing several unrelated jobs, logic in the wrong layer, a change that has to touch many files for one feature. Propose a deeper module only with a clear win.
- Performance: measured problems first. Guesses are suggestions, not findings.
- Readability: names that mislead, comments that lie. No style taste.
3. Prove each finding
- Every finding has a concrete case: "this input or situation leads to this wrong result". No case, no finding.
- Before calling code unused or duplicated, grep the whole tree, including tests, config and dynamic references.
- A shortcut with a comment naming its limit is a decision, not a finding, unless the load already crosses it.
- Propose the smallest fix that solves it, preferring fixes that remove code.
4. Report
Plain words, worst first, in three groups (skip empty ones):
- Must fix: bugs, security, data loss, breaks at the expected load.
- Should fix: risky code without a test, duplication, real slowness, wrong layer.
- Could fix: small, clear improvements.
Each line: file:line, what is wrong, the case that shows it, the fix. End with what you did
not check. If the code is good, say so and say what you checked.
Fixing a large set of findings (dead code, duplicates, structure) is refactor.
Done when
Every changed line was read, every finding has a case and a fix, and the report says what was not checked. When fixing your own findings, each fix gets a test or a look at the running result.
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.

