requesting-code-review

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often ship with undetected bugs, plan deviations, and quality gaps because self-review is biased and context-heavy. This Skill dispatches an independent code reviewer subagent with precisely crafted context to catch Critical and Important issues before they cascade into more work. ## Core Features & Use Cases - Structured Review Dispatch: Fills a reusable prompt template with a description, requirements, and git SHAs so the reviewer evaluates only the work product, not your session history. - Severity-Calibrated Feedback: Returns findings categorized as Critical, Important, and Minor with file:line references, plus a clear merge verdict. - Use Case: After completing a task in subagent-driven development, capture the base and head commit SHAs, dispatch the reviewer, fix Critical and Important issues, then proceed to the next task with confidence. ## Quick Start Ask the AI 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 with a subagent?▼

Get the base and head commit SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer.md template filled with your description, requirements, and SHAs. The reviewer returns strengths, 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, 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 categorizes findings as Critical, Important, or Minor with file:line references and gives a clear ready-to-merge assessment.

When should I not use subagent code review?▼

Skip it for trivial single-line changes or when no subagent support is available in your environment. The Skill is designed for substantive changes where independent evaluation adds value.

What should I do if the code reviewer is wrong?▼

Push back with technical reasoning and show code or tests that prove the implementation works. You can also request clarification rather than accepting invalid feedback.