requesting-code-review

Dispatch a reviewer subagent with git diff ranges and requirement references.

Updated May 9, 2026
One-click install
npx skills add https://github.com/kk20300113-png/my-claude-skills --skill requesting-code-review-kk20300113-png
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/requesting-code-review
Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill requesting-code-review-kk20300113-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unstructured or skipped code reviews let bugs, security flaws, and requirement deviations slip into codebases, causing cascading technical debt and broken functionality that is costly to fix later.

Core Features & Use Cases

  • Structured Review Dispatch: Sends a dedicated code reviewer subagent with precise context (implementation summary, requirements, git diff range) to avoid biased, context-limited reviews.
  • Mandatory Checkpoint Enforcement: Integrates with subagent-driven development, plan execution, and ad-hoc workflows to require reviews after each task, after major feature completion, and before merging to main.
  • Actionable Feedback Categorization: Ensures reviewer output is sorted by severity (Critical, Important, Minor) with clear file references and fix guidance to streamline issue resolution. Use case: A developer building a new data export feature can use this skill to run a review of their changes against the original plan before merging, catching missing edge case handling early.

Quick Start

Use the requesting-code-review skill to review the code changes you just completed for the new user notification system against the requirements in docs/plans/notification-plan.md 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 enforce structured code reviews before merging to production branches?

You can enforce structured code reviews by dispatching a dedicated reviewer subagent with precise git diff ranges and requirement references to generate categorized, actionable feedback before merging to main.

What is the best way to catch requirement deviations and bugs during feature development?

The best way to catch requirement deviations is running context-focused code reviews at mandatory checkpoints after each task, after major feature completion, and pre-merge to prevent technical debt.

Can I integrate peer review checkpoints into a subagent-driven development workflow?

Yes, you can integrate mandatory peer review checkpoints into subagent-driven development workflows, plan execution, and ad-hoc feature work to require reviews after each task and before merging to main.

How does a reviewer subagent categorize code review feedback?

The reviewer subagent categorizes code review feedback by severity levels of Critical, Important, and Minor, providing clear file references and fix guidance to streamline issue resolution.

When do I need to run a code review on my git diff before merging?

You need to run a code review on your git diff at mandatory checkpoints after each task, after major feature completion, and pre-merge to main to catch missing edge case handling early.