requesting-code-review

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

3|Updated Sep 18, 2025
One-click install
npx skills add https://github.com/KingMichaelPark/dotfiles --skill requesting-code-review-kingmichaelpark
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/KingMichaelPark/dotfiles/tree/main/ai/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/KingMichaelPark/dotfiles --skill requesting-code-review-kingmichaelpark

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent review, letting bugs, architectural issues, and missed requirements cascade into later work. This Skill provides a structured workflow for dispatching a code reviewer subagent with precisely crafted context so completed work is verified against its plan before proceeding. ## Core Features & Use Cases - Structured Review Dispatch: Builds a reviewer prompt from a template with placeholders for description, requirements, and git SHAs, keeping the reviewer focused on the work product rather than session history. - Severity-Calibrated Feedback: Returns findings categorized as Critical, Important, and Minor with file:line references, plus a clear merge readiness verdict. - Read-Only Review Safety: Instructs the reviewer to inspect changes via git diff, git show, and git log without mutating the working tree or HEAD. - Use Case: After finishing a feature task, you capture the base and head commit SHAs, dispatch the reviewer subagent with the plan reference, receive categorized feedback, fix Important issues, and continue to the next task. ## 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?

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

Can the code reviewer 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 git worktree in a temporary directory if it needs another revision.

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

Push back with technical reasoning rather than ignoring the feedback. Show code or tests that prove the implementation works, and request clarification from the reviewer when the concern is unclear.