requesting-code-review

Dispatches a read-only code-reviewer subagent to review git diffs against requirements.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/tottenjordan/me-skittles --skill requesting-code-review-tottenjordan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/tottenjordan/me-skittles/tree/main/gemini/requesting-code-review
Command: npx skills add https://github.com/tottenjordan/me-skittles --skill requesting-code-review-tottenjordan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent verification, letting bugs, missing requirements, and architectural issues compound across tasks. This Skill structures the process of requesting an objective code review from a subagent before work proceeds or merges. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a general-purpose subagent with a structured reviewer template that inspects the git diff between two SHAs and never edits code. - Severity-Categorized Feedback: Returns findings grouped as Critical, Important, and Minor issues with file:line references, plus a clear merge-readiness verdict. - Workflow Integration: Defines when to request reviews, including after each task in subagent-driven development, after major features, and before merging to main. - Use Case: After implementing a new feature, you capture the base and head commit SHAs, dispatch the reviewer subagent with the plan requirements, receive categorized feedback, fix Critical and Important issues, and only then continue to the next task. ## Quick Start Ask the agent 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 from an AI agent before merging?▼

Capture the base and head git SHAs, then dispatch a general-purpose subagent using the code-reviewer template with what was implemented and the plan requirements. The subagent reviews the diff and returns categorized findings with 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, or after fixing a complex bug.

Can the code reviewer subagent modify my code?▼

No, the reviewer subagent is read-only by design. It reports findings with file and line references but never edits code, so all fixes remain under your control.

What should I do if the code review feedback is wrong?▼

Push back with technical reasoning rather than blindly implementing suggestions. Show code or tests that prove the current approach works, and request clarification from the reviewer.

What are the limitations of subagent-based code review?▼

The reviewer only sees the git diff range and context you provide, so it can miss issues outside that scope. It also depends on accurate requirement descriptions, and its severity judgments still require your technical judgment.