requesting-code-review

Dispatch a subagent to review code against requirements and quality standards.

63|2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/xhyqaq/superpowers-plus --skill requesting-code-review-xhyqaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/xhyqaq/superpowers-plus/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/xhyqaq/superpowers-plus --skill requesting-code-review-xhyqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the risk of undetected code issues cascading into larger bugs, rework, and production incidents by enforcing structured, focused code reviews at key development checkpoints, rather than relying on ad-hoc self-review that often misses critical flaws.

Core Features & Use Cases

  • Dedicated Subagent Review: Dispatches an isolated general-purpose subagent to evaluate code, keeping the reviewer focused on the work product rather than the developer's thought process, and preserving the developer's context for continued work.
  • Standardized Review Template: Includes a pre-built prompt template that ensures consistent evaluation of plan alignment, code quality, architecture, testing, and production readiness, with clear severity categorization for issues.
  • Workflow Integration: Supports mandatory review checkpoints for subagent-driven development (after each task), executing plans (at natural checkpoints), and ad-hoc development (before merge, when stuck, or before refactoring). For example, after completing a user authentication feature, you can request a review to catch missing edge case handling or security flaws before they reach production.

Quick Start

Use the requesting-code-review skill to review your recent code changes against the associated task requirements before merging to the main branch.

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 before merging changes to the main branch?

Automate pre-merge code review by dispatching a dedicated subagent to evaluate your changes against requirements and quality standards. This enforces structured review checkpoints to catch missing edge cases or security flaws before they reach production.

What is the best way to review code quality after completing a major feature implementation?

The best way to review code quality after a feature implementation is to dispatch a focused subagent using a standardized prompt template. It evaluates plan alignment, architecture, testing coverage, and production readiness, categorizing issues by severity for actionable feedback.

Can I use a subagent for issue triage when my development workflow is stuck?

Yes, you can dispatch a general-purpose subagent for optional issue triage when stuck or before refactoring. The subagent performs an isolated review of the work product, evaluating code quality and architecture while preserving your developer context for continued work.

Does a standardized code review template help catch architecture and testing flaws?

A standardized code review template ensures consistent evaluation of architecture and testing coverage by applying predefined quality standards. It categorizes discovered issues by severity, transforming ad-hoc self-review into actionable, structured feedback.

When do I need a pre-merge check for subagent-driven development tasks?

You need a pre-merge check after completing subagent-driven development tasks, executing plans at natural checkpoints, or ad-hoc development before merging. These mandatory review checkpoints prevent undetected code issues from cascading into larger bugs or production incidents.