Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ganyuanran/requesting-code-review
Use when requesting independent code review, after implementation slices, before merging high-risk work, or when verification exposes evidence, baseline, architecture, compatibility, or retirement uncertainty.
Passed 16 of 19 test cases with the skill, and 8 of 19 without it.
and 12 more in the full report
11 fixed8 passed either way2 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When filling out the reviewer prompt template for a diff that replaces an old feature flag fallback path, which specific placeholder receives the legacy path disposition details?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies RETIREMENT_NOTES as the placeholder for legacy fallback and old owner disposition details | Missed | Passed |
The instructions your model reads when the skill loads.
Dispatch a reviewer subagent using the canonical code-reviewer.md template to
catch issues before they cascade. The reviewer gets precisely crafted context
for evaluation — never your session's history. This keeps the reviewer focused
on the work product, not your thought process, and preserves your own context
for continued work.
This skill is the canonical review-request workflow for method-pack implementation work. Use it to request review only after you have enough evidence, enough context, and a clear authority boundary for what the reviewer is being asked to assess.
Core principle: Review early, review often.
Findings First: Reviews lead with concrete findings before summary. Use bugs first, risk first, tests first. Strengths and general assessment are still useful, but they must not bury correctness, evidence, architecture, or retirement problems.
Review readiness is not merge approval. A review can reduce uncertainty and
recommend readiness, but it does not replace verification-before-completion
and does not grant completion authority.
Mandatory:
Optional but valuable:
Before you leave this workflow, you must be able to state:
test cases passed, vs 8 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.