Requesting code review
Skill charlieviettq/awesome-agent-skill/.claude/skills/requesting-code-review
Curated skill pack for LLM agents in engineer and science workflow (Cursor & Claude ready).
npx -y skills add charlieviettq/awesome-agent-skill --skill requesting-code-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 22 stars22 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Request a focused code review with scope, diff context, and severity-ordered findings. Use before merge or between plan tasks when quality gate is needed.
SKILL.md
2.0 KB, as published. Nobody here has run it
Requesting code review
When to use
- Before landing a significant PR or slice
- After completing a plan task that touches shared contracts
- When risk is high (auth, money, data migration, agent tools)
When not to use
- Trivial typo-only changes with no behavior impact
- User explicitly wants speed over review
Prepare review packet
- Scope — what changed and what was intentionally out of scope
- Base — branch name and commit range or PR link
- Risk areas — files or behaviors reviewers should scrutinize
- Verification already run — commands + outcomes (paste evidence)
- Questions — specific uncertainties for the reviewer
Review request template
## Review request
- **Scope:**
- **Base / range:**
- **Risk areas:**
- **Verification run:**
- **Open questions:**
- **Severity scale:** Critical / High / Medium / Low / Nit
Using a reviewer subagent (optional)
Only when user or parent agent explicitly allows subagents:
- Pass the packet above; do not pass unrelated context
- Ask for findings ordered by severity with file:line references
- Parent agent integrates findings; subagent does not merge or push
For deep structural review, gstack/code-quality/review may be used as an optional supplement.
After review
- Triage findings with
receiving-code-review - Re-run verification before claiming addressed
Anti-patterns
- "Please review everything" with no scope
- Starting review before tests pass locally
- Treating nitpicks as blockers without trade-off discussion
Related
receiving-code-review, verify-before-done, doubt-driven-review, github-comment-triage
Patterns inspired by obra/superpowers (MIT).