requesting-code-review

Name: requesting-code-review
Availability: InStock
Author: yuquanliu1-dot

Dispatch a code-review subagent for a git change set and triage feedback.

Updated Aug 23, 2026

Search Tags:#quality assurance #code review #development workflow #merge readiness #git diff #subagent coordination #severity triage

Ready to run

npx skills add https://github.com/yuquanliu1-dot/Test --skill requesting-code-review-yuquanliu1-dot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/yuquanliu1-dot/Test/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/yuquanliu1-dot/Test --skill requesting-code-review-yuquanliu1-dot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams reduce defects and rework by requesting an organized code review at the right moments in the development and merge workflow.

Core Features & Use Cases

Review dispatch with precise context: Sends a dedicated code-review subagent only the information needed to evaluate the changes (what was implemented, requirements, and the git range).
Focused evaluation and severity triage: Produces categorized feedback (Critical/Important/Minor) and a clear readiness verdict for merge decisions.
Workflow fit: Use after each subagent-driven task, after major features, or before merging to main to prevent issues from cascading.

Quick Start

Request a code review after your latest change by providing the base and head SHAs, a short description of what you implemented, and the plan or requirements it should match.

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 for a specific git diff range before merging?▼

To request a code review, you provide the base and head SHAs of your git diff range, a brief description of the implemented work, and the original plan or requirements to evaluate merge readiness.

When should I integrate an automated code review into my development workflow?▼

You should integrate an automated code review after completing a specific development task, finishing a major feature, or right before merging changes to main to prevent defects from cascading.

How do I perform severity triage on code review feedback?▼

Severity triage categorizes code review feedback into Critical, Important, and Minor levels, allowing you to act on critical and important issues first before proceeding with the merge.

Can I use subagent coordination to evaluate only my latest git changes?▼

Yes, you can dispatch a dedicated code-review subagent by sending only the necessary git change set context, including the implemented work, requirements, and base-to-head diff range.

What is the best way to prevent defects from reaching the main branch?▼

The best way to prevent defects is to request targeted code reviews using precise git diff ranges and requirements context to evaluate merge readiness before changes are integrated into main.