requesting-code-review

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code issues caught late compound into larger problems, and self-review often misses defects in your own work. This Skill provides a structured workflow for dispatching an independent code reviewer subagent that evaluates completed work against its plan before issues cascade. ## Core Features & Use Cases - Subagent-Based Review: Dispatches a general-purpose subagent with a precisely crafted prompt template so the reviewer sees only the work product, not your session history. - Structured Review Template: The code-reviewer.md template enforces severity-calibrated feedback (Critical, Important, Minor) with file:line references and a clear merge verdict. - Git Range Review: Reviews a specific commit range using BASE_SHA and HEAD_SHA, with read-only rules that prevent the reviewer from mutating your working tree. - Use Case: After completing a task in subagent-driven development, capture the base and head commit SHAs, dispatch the reviewer with the template, fix Critical and Important issues, then proceed to the next task. ## Quick Start Ask the AI to request a code review of your latest commits using the code-reviewer template before merging to main.

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

Get the base and head commit SHAs with git rev-parse, then dispatch a general-purpose subagent using the code-reviewer.md template. Fill in the description, requirements, and SHA placeholders so the reviewer evaluates only the relevant diff.

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 working tree?▼

No. The review is strictly read-only on the current checkout. The template instructs the reviewer to use git show, git diff, and git log, and to use a separate git worktree in a temporary directory if another revision is needed.

What feedback format does the code review template produce?▼

The reviewer returns Strengths, Issues categorized as Critical, Important, or Minor with file:line references, Recommendations, and a final Assessment stating whether the work is ready to merge with reasoning.

What should I do if the code reviewer 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 when needed.