requesting-code-review

Request structured code reviews before merging completed changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid shipping flawed implementations by providing a structured process for requesting focused code reviews before changes are merged or expanded.

Core Features & Use Cases

  • Review Workflow Guidance: Creates a repeatable process for dispatching a code reviewer subagent with precise implementation context instead of relying on conversation history.
  • Quality Validation: Ensures completed features, refactors, and bug fixes are evaluated against requirements, architecture standards, testing expectations, and production readiness.
  • Use Case: Before merging a major feature, use this Skill to prepare a reviewer with the relevant git changes, requirements, and evaluation criteria to identify critical and important issues.

Quick Start

Ask the AI to use the requesting-code-review skill to review the completed feature implementation before merging it.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I request a structured code review before merging changes?

A structured code review dispatches a reviewer subagent with precise implementation context, such as git changes and requirements, to evaluate production readiness before merging. This process bypasses conversation history to ensure focused quality validation.

What does a code review subagent evaluate during feature development?

A code review subagent evaluates requirements alignment, code quality, testing coverage, architecture decisions, and production readiness. This ensures completed features, refactors, and bug fixes meet delivery standards before integration.

When do I need to use a code review process in a subagent-driven workflow?

You need a code review process in a subagent-driven workflow when implementation correctness must be verified before merging or expanding changes. It applies to feature development, refactoring, and debugging to catch issues early.

Can I use automated merge validation for refactoring and debugging tasks?

Yes, automated merge validation applies to refactoring and debugging tasks through a structured review process. It evaluates completed changes against architecture standards and testing expectations to ensure delivery quality.

What is the best way to validate code quality and testing coverage before production?

The best way to validate code quality and testing coverage before production is dispatching a reviewer with explicit evaluation criteria. This structured review identifies critical issues by assessing requirements alignment and architecture decisions.