requesting-code-review

Dispatch reviewer subagents to evaluate git diff ranges against requirements.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/wangx7/skills-collection --skill requesting-code-review-wangx7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/wangx7/skills-collection/tree/main/superpowers-main/skills/requesting-code-review
Command: npx skills add https://github.com/wangx7/skills-collection --skill requesting-code-review-wangx7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of undetected code defects and requirement deviations that cascade into costly rework, broken features, and production outages by enforcing structured, focused code reviews at key development checkpoints.

Core Features & Use Cases

  • Focused Review Context: Dispatches dedicated code reviewer subagents with precise change context (git diff ranges, requirement details) instead of full session history, so reviewers focus on the work product, not the implementer's thought process.
  • Mandatory Review Checkpoints: Enforces reviews after every task in subagent-driven development, after major feature completion, and before merging to main, with optional valuable checkpoints for when work is stuck, before refactoring, or after complex bug fixes.
  • Standardized Feedback Framework: Includes a pre-built reviewer prompt template that categorizes issues by severity (Critical, Important, Minor) and requires actionable, specific feedback with file and line references.
  • Use Case Example: A developer building a new payment processing feature can use this Skill after each implementation task to catch missing edge cases or security gaps before they affect subsequent work in the feature branch.

Quick Start

Use the requesting-code-review skill to dispatch a code reviewer subagent to evaluate your recent code changes against project requirements before proceeding with further development work.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I automate code review in a subagent-driven development workflow?

Automate code review in subagent-driven workflows by dispatching dedicated reviewer subagents with precise git diff ranges and requirement context, enforcing mandatory review checkpoints after each task, major feature completion, and before merging to main.

What is the best way to catch code defects and requirement deviations before merging to main?

The best way to catch code defects before merging to main is enforcing structured peer reviews at key development checkpoints, using dedicated reviewer subagents to evaluate git diffs against project requirements to prevent costly rework and production outages.

Does this code review approach work with git diff ranges instead of full session history?

Yes, this code review approach works with git diff ranges, dispatching dedicated reviewer subagents with precise change context and requirement details instead of full session history so reviewers focus on the work product, not the implementer's thought process.

How to categorize code review feedback by severity for actionable peer review?

Categorize code review feedback by severity using a standardized reviewer prompt template that classifies issues into Critical, Important, and Minor levels, requiring actionable, specific feedback with file and line references.

When do I need to run code review checkpoints during feature development?

Run code review checkpoints after every task in subagent-driven development, after major feature completion, and before merging to main, with optional checkpoints when work is stuck, before refactoring, or after complex bug fixes.

Can I use this structured code review skill for ad-hoc feature work?

Yes, you can use this structured code review skill for ad-hoc feature work, as it applies to all software development workflows including subagent-driven development, plan execution, and ad-hoc feature work to eliminate undetected code defects.