requesting-code-review

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

2|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/MoofonLi/dev-ready --skill requesting-code-review-moofonli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/MoofonLi/dev-ready/tree/main/src/dev_ready/templates/claude/skills/requesting-code-review
Command: npx skills add https://github.com/MoofonLi/dev-ready --skill requesting-code-review-moofonli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed code often goes unreviewed or is reviewed superficially by the same agent that wrote it, letting bugs and plan deviations cascade into later work. This Skill enforces a structured, independent review step using a dedicated reviewer subagent with precisely crafted context. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a general-purpose reviewer subagent with a ready-made prompt template, keeping the diff evaluation out of your main session's context window. - Severity-Calibrated Feedback: The reviewer returns Strengths, Critical/Important/Minor issues with file:line references, Recommendations, and a clear merge verdict. - Git Range Targeting: Reviews a precise commit range using BASE_SHA and HEAD_SHA, with read-only rules that forbid mutating the working tree. - Use Case: After finishing a task in a multi-step implementation plan, capture the base and head commit SHAs, dispatch the reviewer with the plan requirements, fix any Critical or Important findings, then proceed to the next task with confidence. ## Quick Start Ask your agent to request a code review of the changes between the previous commit and HEAD using the code-reviewer template before continuing to the next task.

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 from an AI agent before merging?

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, the requirements, and both 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 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 in a git diff?

The reviewer checks plan alignment, code quality, architecture, testing, and production readiness across the specified commit range. It reports strengths, issues categorized as Critical, Important, or Minor with file:line references, and a clear merge assessment.

Can the code reviewer subagent modify my working tree?

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 another revision checked out.

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

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