requesting-code-review

Dispatches a read-only reviewer subagent to evaluate git diffs against requirements.

Updated Aug 20, 2026
One-click install
npx skills add https://github.com/Pega88/agy-superpowers --skill requesting-code-review-pega88
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Pega88/agy-superpowers/tree/main/.agents/plugins/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/Pega88/agy-superpowers --skill requesting-code-review-pega88

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent verification, letting bugs, plan deviations, and quality issues cascade into later work. This Skill provides a structured workflow for requesting an independent code review from a subagent before merging or continuing development. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a read-only reviewer subagent with a precisely crafted prompt template, keeping the review out of your main context window. - Structured Feedback Format: Returns findings categorized as Strengths, Critical, Important, and Minor issues, plus a clear merge-readiness verdict. - Git Range Targeting: Reviews a specific commit range using BASE_SHA and HEAD_SHA so feedback is scoped to the exact changes made. - Use Case: After completing a task in a multi-step implementation plan, capture the base and head commits, dispatch the reviewer with the task requirements, fix any Critical or Important issues, then proceed to the next task with confidence. ## Quick Start Ask the agent 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 for my changes before merging?

Get the base and head commit SHAs with git rev-parse, then dispatch a reviewer subagent using the code-reviewer template with a description, the requirements, and the commit range. The reviewer returns categorized issues and a merge 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 useful when stuck, before refactoring, or after fixing a complex bug.

Can the code reviewer subagent modify my working tree?

No. The reviewer operates read-only on the checkout and must not mutate the working tree, index, HEAD, or branch state. It inspects history with git show, git diff, and git log, using a separate worktree only if needed.

What should I do when the code review reports issues?

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.

Why dispatch a reviewer subagent instead of reviewing the diff myself?

Reviewing inline consumes the context window you need to coordinate the work. A subagent keeps the diff and evaluation in its own context, returning only the findings so you can keep driving the implementation.