requesting-code-review

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

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/kangjuhyup/study --skill requesting-code-review-kangjuhyup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/kangjuhyup/study/tree/main/scoped-superpowers-ab/workflow-code-benchmark/fixture/workflows/full/skills/requesting-code-review
Command: npx skills add https://github.com/kangjuhyup/study --skill requesting-code-review-kangjuhyup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Completed code changes often go unreviewed or get shallow self-review, letting bugs and plan deviations cascade into later work. This Skill structures the review handoff so a dedicated reviewer subagent evaluates the diff with fresh context. ## Core Features & Use Cases - Structured Review Dispatch: Provides a repeatable workflow for capturing base/head SHAs and dispatching a general-purpose reviewer subagent with precisely crafted context. - Reviewer Prompt Template: Ships a ready-to-fill template (code-reviewer.md) covering plan alignment, code quality, architecture, testing, and production readiness, with severity-calibrated output (Critical / Important / Minor). - Use Case: After finishing a feature task, you run git rev-parse to get the base and head SHAs, fill the template placeholders, and receive a verdict of Ready to merge: Yes, No, or With fixes before continuing. ## Quick Start Ask the AI to request a code review of the changes between the previous commit and HEAD using the code-reviewer template.

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. Fill in the description, requirements, and SHA placeholders, and the reviewer returns strengths, 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 useful 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 reviewer uses git show, git diff, and git log, and may only inspect other revisions via a separate temporary worktree, never by moving HEAD.

What should I do when the code review finds Critical issues?

Fix Critical issues immediately and resolve Important issues before proceeding. Minor issues can be noted for later. If you believe the reviewer is wrong, push back with technical reasoning and code or tests that prove the behavior.

Why not review the diff myself instead of dispatching a reviewer?

Reviewing inline consumes the context window you need to coordinate the work. A reviewer subagent keeps the diff and evaluation in its own context, returning only the findings so you can keep driving the task.