review
Skill0 starsChanged 3 months agoMITView on GitHub
use this skill when user asks for code review or QA.
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 repository24 other files it gives its agents.
- corporate-espionageSkill
- dispatching-parallel-agentsSkill
- epub-readerSkill
- executing-plansSkill
- finishing-a-development-branchSkill
- github-raw-readerSkill
- magisk-moduleSkill
- notepadpp-plugin-skillSkill
- planningSkill
- receiving-code-reviewSkill
- requesting-code-reviewSkill
- skill-creator2Skill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- technical-writerSkill
- test-driven-developmentSkill
- text-humanizerSkill
- using-git-worktreesSkill
- using-superpowersSkill
- verification-before-completionSkill
- windows-diagnosticsSkill
- writing-plansSkill
- zed-extensionSkill
- zed-themeSkill
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 10
Do not limit analysis to recent changes.
- Distinctive: line 41
No severity grouping or ranking
- Distinctive: line 42
No confidence scores in output
- Distinctive: line 43
No clustering: one entry per distinct finding, per location
“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
Scope
Review every file, module, and dependency declaration in the repository. Do not limit analysis to recent changes.
Focus areas
- Discoverability: naming clarity, module structure, entry points, export surfaces, undocumented APIs
- Code quality: duplication, dead code, unnecessary abstractions, poor separation of concerns
- Optimization: redundant computation, avoidable re-renders or re-allocations, inefficient data structures
- Performance: I/O bottlenecks, blocking calls, memory pressure, missing caching, expensive operations in hot paths
- Bugs: logic errors, unhandled nulls, race conditions, silent failures, unchecked edge cases
Slop detection
Flag every instance of: valueless boilerplate, copy-paste code, over-engineered patterns, no-op abstractions, unused variables or exports, reimplementations of stdlib or utility functions, and misleading or stale comments.
Confidence threshold
Report all findings with confidence >= 50. Do not suppress findings for being stylistic or minor — surface everything.
Output rules
- Produce a single .md file
- No positive observations
- No severity grouping or ranking
- No confidence scores in output
- No clustering: one entry per distinct finding, per location
- Maximize finding count — do not consolidate related findings
- Recommendation per finding: one line only, stating what to do, not how to do it
Entry format
[file/path:LINE] Description of the issue or slop pattern.
Fix: one-line recommendation.
use ./docs/code-review.md for: Review a pull request or a set of code changes for bugs, logic errors, and project-convention violations using a confidence-filtered, multi-agent process. Use this skill when the user asks to review a PR, audit pending changes, or inspect a diff for problems before merging.
use ./docs/code-reviewer.md for: Review code for bugs, logic errors, security vulnerabilities, code quality issues, and adherence to project conventions, using confidence-based filtering to report only high-priority issues that truly matter. Use this skill when reviewing a small set of changes locally (such as unstaged diff), when dispatched as a sub-task during feature-dev quality review, or when the user wants a critique of a specific file or function.
use ./docs/quality-assurance.md for: Comprehensive testing and validation strategies for spec-driven development. Learn phase-specific validation techniques, quality gates, and testing approaches to ensure high-quality implementation
use ./docs/security-review.md for: Perform a focused security review of pending git changes to identify high-confidence security vulnerabilities with real exploitation potential. Use this skill when the user asks for a security review, security audit, vulnerability scan, or wants to check pending changes on a branch for security issues before merging. This is NOT a general code 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.

