requesting-code-review

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

Updated Jul 4, 2024
One-click install
npx skills add https://github.com/hareki/dotfiles --skill requesting-code-review-hareki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/hareki/dotfiles/tree/main/agents/.agents/skills/requesting-code-review
Command: npx skills add https://github.com/hareki/dotfiles --skill requesting-code-review-hareki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often get merged without independent verification, letting bugs, plan deviations, and quality issues compound across tasks. This Skill provides a structured workflow for dispatching a code reviewer subagent with precisely scoped context so completed work is validated against its requirements before it cascades. ## Core Features & Use Cases - Structured Review Dispatch: Builds a reviewer prompt from a template with placeholders for description, requirements, and git base/head SHAs. - Severity-Calibrated Feedback: Returns findings categorized as Critical, Important, and Minor with file:line references and a clear merge verdict. - Read-Only Review Safety: Instructs the reviewer to inspect history via git diff, git show, and git log without mutating the working tree or HEAD. - Use Case: After finishing a task in subagent-driven development, capture the base and head commit SHAs, dispatch the reviewer subagent with the plan reference, fix Critical and Important issues, then proceed 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 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 useful 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 returns strengths, issues categorized as Critical, Important, or Minor with file:line references, recommendations, and a merge readiness verdict.

Can the reviewer subagent modify my code during review?▼

No. The template enforces a read-only review: the reviewer uses git show, git diff, and git log to inspect history and must never mutate the working tree, index, HEAD, or branch state. Alternate revisions are inspected via a temporary git worktree.

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

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