requesting-code-review

Dispatch a code reviewer subagent to evaluate changes against requirements and a git diff range.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/yashs33244/my-mac-claude --skill requesting-code-review-yashs33244
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/superpowers/requesting-code-review
Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill requesting-code-review-yashs33244

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you prevent defects from spreading by getting a second agent to evaluate your code changes against the plan before you continue or merge.

Core Features & Use Cases

  • Early, often review cadence: Request review after each subtask, after major features, and before merge.
  • Precisely scoped context: Reviews are driven by a description, requirements, and an explicit git range rather than your full session history.
  • Actionable feedback loop: Classifies issues by severity and supports targeted fixes, including pushing back when feedback is incorrect.
  • Use case: Implementing a major feature via subagent-driven development, then dispatching a reviewer to confirm the result matches the plan and is production-ready.

Quick Start

Request a code review by providing a short build description, the plan or requirements, and the git base/head SHAs for the change you completed.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I get an automated code review against my requirements before merging?

Automated code review against requirements is done by dispatching a reviewer subagent to evaluate your git diff range and build description, categorizing issues by severity before merge.

What information do I need to provide to run a pre-merge code review on my git diff?

To run a pre-merge code review on your git diff, you provide a short build description, the plan or requirements, and the base and head commit SHAs for the completed changes.

Can I use a subagent to validate code changes without sharing my full session history?

Yes, you can use a subagent to validate code changes with secure context isolation by providing an explicit git range and description rather than your full session history.

When should I request a code review during subagent-driven development?

Request a code review during subagent-driven development after completing each subtask, finishing major features, and as a final pre-merge validation step to catch issues early.

How does a code reviewer subagent classify issues found in a git diff?

A code reviewer subagent classifies issues found in a git diff by severity, creating an actionable feedback loop that supports targeted fixes or pushing back on incorrect feedback.