requesting-code-review

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

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill requesting-code-review-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill requesting-code-review-cyrus-pinto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed code changes often go unreviewed or get superficial self-review, letting bugs and plan deviations cascade into later work. This Skill structures the process of dispatching an independent code reviewer subagent with precisely crafted context so issues are caught early. ## Core Features & Use Cases - Structured Review Dispatch: Provides a complete reviewer prompt template covering plan alignment, code quality, architecture, testing, and production readiness. - Severity-Calibrated Feedback: The reviewer returns findings categorized as Critical, Important, and Minor with file:line references and a clear merge verdict. - Context Isolation: The reviewer receives only the git diff range and requirements, never the session history, keeping evaluation focused on the work product. - Use Case: After finishing a feature task, you capture the base and head commit SHAs, dispatch the reviewer subagent with the template, and fix any Critical or Important issues before proceeding to the next task or merging to main. ## Quick Start Request a code review of my last commit range using the code reviewer template before I merge this feature branch.

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 subagent?

Capture the base and head commit SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer template. Fill in the description, requirements, and SHA placeholders so the reviewer evaluates the exact diff 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, or after fixing a complex bug.

What does the code reviewer check in a git diff?

The reviewer checks plan alignment, code quality, architecture, testing coverage, and production readiness. It returns strengths, issues categorized as Critical, Important, or Minor with file:line references, recommendations, and a merge readiness verdict.

Should the reviewer subagent see my full session history?

No. The reviewer receives only precisely crafted context: a description, the requirements, and the git SHA range. Keeping session history out keeps the review focused on the work product rather than your reasoning process.

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 pushback with evidence is encouraged.