requesting-code-review

Dispatch a read-only code-review subagent with implementation summaries and git ranges.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes code-review requests by automatically packaging the necessary context and dispatching a read-only reviewer, preventing leakage of session history and keeping the focus on the work product.

Core Features & Use Cases

  • Trigger a read-only code-review to evaluate new work after each task or major feature.
  • Ensure feedback targets the implemented code and meets project standards.
  • Useful before merging to main, or when seeking external input from a reviewer.

Quick Start

Dispatch the superpowers-code-reviewer subagent after completing a task using the code-reviewer template to initiate the review.

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 requests before merging to main?

You can automate code review requests by packaging the implementation summary and git range into a standard request, then dispatching a read-only reviewer subagent to evaluate the work before integration.

When should I trigger a code review in a subagent-driven development workflow?

Trigger a code review after completing each subagent task, finishing major features, or before merging to main, ensuring feedback targets the implemented code and meets project quality standards.

How does a read-only code reviewer subagent work?

A read-only code reviewer subagent works by receiving a packaged review request with implementation context and git range, evaluating the work product without modifying code or accessing session history.

What is the best way to standardize pull request reviews for quality assurance?

Standardize pull request reviews by using a code-reviewer template to package implementation summaries and git ranges into uniform requests, dispatching a read-only subagent for consistent feedback.

Can I use a subagent to review code without leaking session history?

Yes, dispatching a read-only reviewer subagent isolates the code review process, preventing session history leakage while keeping the reviewer focused strictly on the work product and project standards.