requesting-code-review

Dispatch a code reviewer subagent to evaluate git changes against requirements before merging.

Updated May 28, 2026
One-click install
npx skills add https://github.com/mpmf/SDD_Base --skill requesting-code-review-mpmf
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/mpmf/SDD_Base/tree/main/.opencode/skills/superpowers/requesting-code-review
Command: npx skills add https://github.com/mpmf/SDD_Base --skill requesting-code-review-mpmf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code issues caught late compound into larger problems. This Skill provides a structured workflow for requesting code reviews from a dedicated reviewer subagent, ensuring completed work is verified against requirements before merging or moving to the next task. ## Core Features & Use Cases - Subagent-Based Review: Dispatch a general-purpose reviewer subagent with precisely crafted context (description, requirements, git SHAs) so it evaluates the work product, not your session history. - Reusable Reviewer Template: A ready-made prompt template (code-reviewer.md) that checks plan alignment, code quality, architecture, testing, and production readiness, returning severity-categorized feedback. - Severity-Calibrated Feedback: Issues are classified as Critical, Important, or Minor with file:line references, plus a clear merge verdict. - Use Case: After finishing a feature task, capture the base and head commit SHAs, dispatch the reviewer subagent with the template, fix Critical and Important issues, then proceed to the next task with confidence. ## Quick Start Ask the AI to request a code review of the changes between the previous commit and HEAD using the code reviewer template before merging.

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 code review for my changes before merging?▼

Get the base and head commit SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer.md template filled with your change description, requirements, and SHAs. The reviewer returns categorized issues and a merge verdict.

When should I request a code review during development?▼

Request review after each task in subagent-driven development, after completing major features, and before merging to main. It is also valuable when stuck, before refactoring, or after fixing a complex bug.

What does the code reviewer subagent check?▼

The reviewer checks plan alignment, code quality, architecture, testing coverage, and production readiness. It categorizes findings as Critical, Important, or Minor with file:line references and gives a clear ready-to-merge assessment.

What should I do if the code reviewer feedback is wrong?▼

Push back with technical reasoning rather than accepting incorrect feedback. Show code or tests that prove the implementation works, and request clarification from the reviewer on disputed points.

Why use a separate subagent for code review instead of self-review?▼

A separate reviewer subagent receives only the crafted context (description, requirements, git range), keeping it focused on the work product rather than your session history. This also preserves your own context window for continued work.