requesting-code-review

Automates AST-powered code review and repair for developers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of undetected code defects and requirement mismatches that are caught too late in the development cycle, leading to costly post-merge rework, production bugs, and delayed project timelines.

Core Features & Use Cases

  • Dedicated Reviewer Subagent Dispatch: Spins up a focused code reviewer with only the precise change context (no session history noise) to evaluate your work product objectively.
  • Structured Review Workflow: Includes mandatory review checkpoints after each subagent task, after major feature completion, and pre-merge, plus optional reviews when stuck, before refactoring, or after fixing complex bugs.
  • Feedback Triage Guidance: Clear rules to prioritize fixes for critical, important, and minor issues, plus guidance to push back on incorrect feedback with technical reasoning.
  • Use Case: For a team building a new payment processing feature, use this Skill to run a review after each implementation task to catch missing edge cases before they compound across the codebase.

Quick Start

Use the requesting-code-review skill to dispatch a code review for your latest changes to the payment processing feature, using the commit from the start of the feature work as the base comparison point.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate code review dispatch to catch defects before merging to main?

To automate code review dispatch, use this Skill to spin up a dedicated reviewer subagent with precise git diff context, evaluating changes objectively without session history noise to catch defects before merging to main.

When should I run a code review in my software development workflow?

Run code reviews at mandatory checkpoints after each subagent task, after major feature completion, and pre-merge, plus optional reviews when stuck, before refactoring, or after fixing complex bugs to prevent requirement mismatches.

How do I triage code review feedback by severity level?

Triage code review feedback by severity level using structured rules to prioritize fixes for critical, important, and minor issues, and push back on incorrect feedback with technical reasoning when necessary.

Can I review code changes using only the git diff context?

Yes, you can review code changes using only the git diff context by dispatching a focused code reviewer subagent that receives precise change context isolated from session history noise for objective evaluation.

What is the best way to prevent post-merge rework and production incidents?

The best way to prevent post-merge rework and production incidents is to apply a structured code review workflow at mandatory checkpoints after each implementation task to catch missing edge cases early.

How do I push back on incorrect code review feedback with technical reasoning?

Push back on incorrect code review feedback with technical reasoning by using the provided feedback triage guidance, which helps you evaluate severity levels and articulate why specific reviewer feedback is incorrect.