requesting-code-review

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

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/em411/supercodex --skill requesting-code-review-em411
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/em411/supercodex/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/em411/supercodex --skill requesting-code-review-em411

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often ship with undetected bugs, plan deviations, or quality gaps because self-review misses issues. This Skill provides a structured process for dispatching an independent code reviewer subagent that evaluates completed work against its requirements before problems cascade into later tasks. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a general-purpose reviewer subagent with a precisely crafted prompt template, keeping the reviewer focused on the work product rather than your session history. - Severity-Calibrated Feedback: Returns findings categorized as Critical, Important, or Minor, with file:line references, plus strengths, recommendations, and a clear merge verdict. - Read-Only Review Safety: Instructs the reviewer to inspect git history without mutating the working tree, index, or HEAD. - Use Case: After completing a task in subagent-driven development, capture the base and head SHAs, dispatch the reviewer with the plan requirements, fix Critical and Important issues, then proceed to the next task. ## Quick Start Ask Claude 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 completed work?

Get the base and head git SHAs for the change range, then dispatch a general-purpose subagent using the code-reviewer.md template. Fill in the description, plan or requirements, and both SHAs so the reviewer can run git diff on the exact range.

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, and production readiness. It returns strengths, issues categorized as Critical, Important, or Minor with file:line references, recommendations, and a clear merge readiness verdict.

Can the code reviewer modify my working tree or git state?

No. The review is strictly read-only on the current checkout. The reviewer uses git show, git diff, and git log to inspect history, and must use a separate temporary worktree if it needs a different revision.

What should I do if I disagree with the code review feedback?

Push back with technical reasoning and show code or tests that prove the implementation works. Fix Critical issues immediately and Important issues before proceeding, but valid disagreement with evidence is explicitly supported.