requesting-code-review

Dispatches a code-reviewer subagent to evaluate git diffs against requirements before merging.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Pgooone/oh-pgone-claudecode --skill requesting-code-review-pgooone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Pgooone/oh-pgone-claudecode/tree/main/.claude/plugins/cache/superpowers-marketplace/superpowers/5.0.6/skills/requesting-code-review
Command: npx skills add https://github.com/Pgooone/oh-pgone-claudecode --skill requesting-code-review-pgooone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent verification, letting bugs and architectural issues compound across tasks. This Skill provides a structured workflow for requesting an independent code review of your work using a dedicated reviewer subagent with precisely scoped context. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a code-reviewer subagent with a clean context containing only the git diff, requirements, and description, keeping the reviewer focused on the work product. - Severity-Categorized Feedback: Returns issues classified as Critical, Important, or Minor with file:line references, plus a clear merge-readiness verdict. - Workflow Integration: Defines mandatory review checkpoints after each task in subagent-driven development, after major features, and before merging to main. - Use Case: After completing a feature task, you capture the base and head git SHAs, dispatch the reviewer with the plan reference, receive categorized feedback, fix Critical and Important issues, and then proceed to the next task. ## Quick Start Ask the AI to request a code review of the changes between the previous commit and HEAD using the code-reviewer template before continuing to the next task.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I request a code review before merging changes?▼

Capture the base and head git SHAs with git rev-parse, then dispatch the code-reviewer subagent with what was implemented, the plan reference, and the SHA range. The reviewer returns categorized issues and a merge-readiness verdict.

When should I request a code review during development?▼

Request review after each task in subagent-driven development, after completing a major feature, and before merging to main. It is also valuable when stuck, before refactoring, or after fixing a complex bug.

Why use a separate subagent for code review instead of self-review?▼

The reviewer subagent receives only the git diff and requirements, never your session history. This keeps the reviewer focused on the work product rather than your reasoning, and preserves your own context for continued work.

What should I do with code review feedback?▼

Fix Critical issues immediately and Important issues before proceeding, while noting Minor issues for later. If you believe the reviewer is wrong, push back with technical reasoning and code or tests that prove the implementation works.

What are the limitations of subagent-based code review?▼

The reviewer only sees the diff range and context you provide, so incomplete SHA ranges or missing requirements can produce gaps in coverage. It also depends on accurate severity categorization, so you should verify verdicts against actual test results.