requesting-code-review

Dispatches a code reviewer subagent to evaluate git diffs against requirements before merging.

Updated Sep 19, 2026
One-click install
npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill requesting-code-review-ab0umar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/Ab0umar/selrs.cc.BU/tree/main/.codex/plugins/cache/openai-curated/superpowers/dc902811/skills/requesting-code-review
Command: npx skills add https://github.com/Ab0umar/selrs.cc.BU --skill requesting-code-review-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code issues caught late compound into larger problems, and self-review often misses defects in your own work. This Skill provides a structured workflow for requesting an independent code review of completed changes before they merge or cascade into subsequent tasks. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a fresh code reviewer subagent with precisely crafted context (description, requirements, git SHAs) instead of your session history, keeping the reviewer focused on the work product. - Structured Review Template: Ships a reusable code-reviewer.md prompt template that checks plan alignment, code quality, architecture, testing, and production readiness, returning severity-categorized findings (Critical / Important / Minor). - Workflow Integration: Defines mandatory review checkpoints for subagent-driven development, plan execution, and pre-merge verification. - Use Case: After finishing a feature task, you capture the base and head commit SHAs, dispatch the reviewer subagent with the template, receive categorized feedback, fix Critical and Important issues, and then proceed to the next task. ## Quick Start Ask the AI to request a code review of the changes between the previous commit and HEAD using the code reviewer template.

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 before merging changes?▼

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

When should I request a code review during development?▼

Request review after each task in subagent-driven development, after completing a major feature, and before merging to main. It is also valuable when stuck, before refactoring as a baseline check, 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 outputs strengths, issues categorized as Critical, Important, or Minor with file:line references, recommendations, and a clear merge assessment.

Why dispatch a separate subagent instead of reviewing in the same session?▼

A separate subagent receives only the crafted review context, not your session history, so it evaluates the work product rather than your reasoning. This also preserves your own context window for continued implementation work.

What should I do if the code reviewer is wrong about an issue?▼

Push back with technical reasoning and show code or tests that prove the implementation works. You can also request clarification, but never ignore valid Critical or Important feedback without justification.