requesting-code-review
Skill85 starsChanged 6 months agoApache-2.0View on GitHub
Use this skill at Step 8 of the v2 SOP after Verify passes, to request and receive a code review from a Reviewer-Agent (or human reviewer). Packages the diff with context (task documents, specs, COMPLIANCE_TAG, design rationale), invokes the review, and iterates with systematic-debugging until all feedback is closed. Chinese trigger examples: "请求 review", "Step 8", "代码审查", "请人 review", "review 这个 change". Do NOT use as substitute for Step 10 compliance review, do NOT skip when reviewer feedback contains High items. Success = all reviewer feedback closed, review thread archived.
187 other projects use a version of this.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- Lucface/claude-skillstheir own version, first seen Nov 16, 2026
- Floppa2003/skillstheir own version, first seen Nov 16, 2026
- Badhon-00/MDCPtheir own version, first seen Nov 16, 2026
- roronoazoroshao369/vibe-coding-ostheir own version, first seen Nov 15, 2026
- mintunitish/tandemtheir own version, first seen Nov 15, 2026
Used with
Projects with it also use chinese-code-review, chinese-commit-conventions 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.
Leodorareluctant259Skillchinese-code-review
中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈
Also in 8 projects that use this
Leodorareluctant259Skillchinese-commit-conventions
中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化
Also in 8 projects that use this
obraSkilldiagnosing-superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
Also in 20 projects that use this
math-incSkillheartmula
Set up and run HeartMuLa, the open-source music generation model family (Suno-like). Generates full songs from lyrics + tags with multilingual support.
Also in 9 projects that use this
Tommy-ywSkillwebhook-subscriptions
Create and manage webhook subscriptions for event-driven agent activation, or for direct push notifications (zero LLM cost). Use when the user wants external services to trigger agent runs OR push notifications to chats.
Also in 5 projects that use this
math-incSkillminecraft-modpack-server
Set up a modded Minecraft server from a CurseForge/Modrinth server pack zip. Covers NeoForge/Forge install, Java version, JVM tuning, firewall, LAN config, backups, and launch scripts.
Also in 5 projects that use this
- +3 more from Leodorareluctant259
- +2 more from math-inc
Other versions187 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 187
- obra/superpowers★ 314ksame name
- NousResearch/hermes-agent★ 264ksame name
- jnMetaCode/superpowers-zh★ 8.5ksame name
- openai/plugins★ 7.8ksame name
- farm-fe/farm★ 5.6ksame name
- lingyired/status-trio★ 2ksame name
- GanyuanRan/Aegis★ 1.4ksame name
- pcvelz/superpowers★ 1.3ksame name
- math-inc/OpenGauss★ 1.3ksame name
- DemonDamon/AgenticX★ 1.1ksame name
177 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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ask-questions-if-underspecifiedSkill
- audit-snapshot-microSkill
- audit-snapshotSkill
- compliance-precheckSkill
- compliance-reviewSkill
- memory-curateSkill
- mocking-stubbingSkill
- openspec-apply-changeSkill
- openspec-continue-changeSkill
- openspec-new-changeSkill
- openspec-verify-changeSkill
- phi-desensitizeSkill
- prd-authorSkill
- prd-implementation-precheckSkill
- prd-precheckSkill
- prdSkill
- prompt-injection-scanSkill
- quick-fixSkill
- systematic-debuggingSkill
- task-decompositionSkill
- tdd-alignmentSkill
- test-data-generationSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 174 edited versions we read keep these.
1
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 30
When asking for a review, always include:
“Common” is measured: kept by at least 6 in 10 of the 174 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
Requesting Code Review
The "second pair of eyes" gate. Functional, not compliance — that's Step 10.
Review packet contents
When asking for a review, always include:
- The diff (limited to the task's ≤ 2 files)
- The task document
- The relevant spec id(s)
- Reference to design.md and (if applicable) ARCH_INPUT_INDEX
- The PHI handling note (if L3/L4)
What the reviewer checks
| Layer | Examples |
| Correctness | matches spec; covers acceptance criteria |
| Code health | readable, lean (no dead code, no extra comments) |
| Security | input validation, error handling at boundaries, injection surface |
| Maintainability | tests align, naming sensible |
| Reuse | did the author miss an existing utility (reference/legacy-utilities-index.md)? |
Workflow
- Compose review packet.
- Dispatch to Reviewer-Agent (with heterogeneous model — DON'T use coder's model) or to a human.
- Capture feedback in
REVIEW_THREAD.md. - For each feedback item: classify Critical / Major / Minor.
- Address Critical + Major via
systematic-debugging. - Minor: address or accept-and-record.
- Close when all Critical and Major are closed.
Common failure modes
- Self-review on same model — coder and reviewer share model = correlated blind spots. Mitigation: enforce heterogeneity.
- Drive-by approvals — reviewer skims and approves. Mitigation: require explicit checklist signoff.
- Long-running review threads — drags. Mitigation: 24h SLA; auto-escalate.
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.

