requesting-code-review
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.
npx skills add charliehzm/medharness --skill requesting-code-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 | Exam
What does the requesting-code-review skill do?
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.
How do I install it?
Run `npx skills add charliehzm/medharness --skill requesting-code-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From charliehzm/medharness, a repository with 96 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.