superpower-review

Dispatch a code-reviewer subagent to evaluate Git changes for production readiness.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fernandoxavier02/Codex-superpower --skill superpower-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: superpower-review
Source: https://github.com/fernandoxavier02/Codex-superpower/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/fernandoxavier02/Codex-superpower --skill superpower-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Checks and improves code quality and readiness by automatically initiating a dedicated code-review process before merge, keeping the focus on the artifact rather than the developer's thought process.

Core Features & Use Cases

  • Automated Review Dispatch: Launch a code-reviewer subagent via spawn_agent with precise task context and Git SHAs.
  • Contextual, Focused Evaluation: The reviewer analyzes the changes using a narrow, artifact-centric context, preserving your session state.
  • Structured Output & Guardrails: Provides a standardized review report with strengths, issues, and recommendations to guide decisions.
  • Use Case: Before merging major features, after significant task completions, or when seeking a fresh perspective on complex changes.

Quick Start

Dispatch a code-reviewer by running spawn_agent with the specifics and Git SHAs to trigger a structured review.

Frequently Asked Questions about superpower-review

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

FAQPage Schema
How do I automate code review for production readiness before a merge?

To automate code review for production readiness, dispatch a reviewer subagent using spawn_agent with specific Git SHAs. This enforces a comprehensive evaluation of code quality, architecture, and testing before merging to main.

What is subagent-driven code review in LLM collaboration?

Subagent-driven code review in LLM collaboration dispatches a dedicated reviewer subagent to evaluate changes artifact-by-artifact. It preserves your main session state while applying a structured prompt to assess production readiness.

How do I trigger a code review using a specific Git range?

To trigger a code review using a Git range, run spawn_agent and provide the precise task context alongside the Git SHAs. The reviewer subagent then analyzes the specified changes to generate a standardized report.

Does automated code review work after every task completion in subagent development?

Yes, automated code review works after each task completion in subagent-driven development. It applies a defined Git range to evaluate production readiness and outputs structured recommendations before merging to main.

Can I get a structured output format for code quality and architecture evaluation?

Yes, you can get a structured output format for code quality and architecture evaluation. The reviewer subagent enforces standardized guardrails to deliver a report containing strengths, issues, and recommendations.

What are the limitations of using a subagent for code review?

A limitation of using a subagent for code review is its narrow, artifact-centric context. It focuses strictly on the code changes within the specified Git range rather than the developer's thought process.