requesting-code-review

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

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill requesting-code-review-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/ibytechaos/claude/tree/main/plugins/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/ibytechaos/claude --skill requesting-code-review-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent verification, letting bugs, architecture flaws, and unmet requirements slip into production. This Skill structures the review request process so every task or feature gets evaluated by a dedicated reviewer subagent with precisely crafted context. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a superpowers:code-reviewer subagent with a filled template containing what was implemented, the plan, and git SHAs, keeping the reviewer focused on the work product. - Severity-Categorized Feedback: Returns issues classified as Critical, Important, or Minor with file:line references, plus a clear merge-readiness verdict. - Workflow Integration: Defines mandatory review points for subagent-driven development, plan execution, and pre-merge checks. - Use Case: After completing a feature task, you capture the base and head commit SHAs, dispatch the reviewer with the requirements, receive categorized feedback, fix Critical and Important issues, then proceed to the next task. ## Quick Start Ask the AI to request a code review of your latest commits using the code-reviewer template before merging to main.

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 a feature branch?

Capture the base and head commit SHAs with git rev-parse, then dispatch the code-reviewer subagent with what was implemented, the requirements, and the SHA range. The reviewer returns categorized issues and a merge verdict.

What information does a code review subagent need?

The reviewer needs five inputs: what was implemented, the plan or requirements, the base SHA, the head SHA, and a brief description. It then runs git diff over that range and evaluates quality, architecture, testing, and requirement coverage.

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, or after fixing a complex bug.

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

Push back with technical reasoning rather than ignoring the feedback. Show code or tests that prove the implementation works, and request clarification on the reviewer's concern.

How are code review issues prioritized?

Issues are categorized as Critical (must fix immediately), Important (fix before proceeding), and Minor (note for later). Each issue includes a file:line reference, why it matters, and how to fix it.