requesting-code-review

Dispatch a code reviewer subagent to evaluate work against requirements using a standardized template.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates and standardizes the review process by dispatching a code reviewer subagent to catch issues early, preventing defects from cascading into later stages.

Core Features & Use Cases

  • Structured evaluation: Uses a standardized code-review template to assess completed work against requirements.
  • Contextual feedback: Anchors feedback to precise Git ranges (BASE_SHA / HEAD_SHA) and highlights actionable improvements.
  • Workflow integration: Suits subagent-driven development, feature rollouts, and pre-merge validation to improve quality before delivery.

Quick Start

Request a code review after finishing a major task to ensure readiness for merge.

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 reviews before a merge?

Automate code reviews before a merge by dispatching a reviewer subagent to evaluate completed work against requirements using a standardized template. This catches issues early and ensures readiness for delivery.

What is subagent-driven code review and how does it work?

Subagent-driven code review works by dispatching a subagent to evaluate completed work against requirements and catch issues before they cascade. It enforces structured feedback through a standardized template.

How do I provide context for a code review using Git commit SHAs?

Provide context for a code review using Git commit SHAs by supplying baseline and head commit SHAs (BASE_SHA / HEAD_SHA). This anchors the evaluation to precise Git ranges and highlights actionable improvements.

Can I use this code review process for feature rollouts and pre-merge validation?

Yes, you can use this code review process for feature rollouts and pre-merge validation. It is designed to suit subagent-driven development workflows to improve quality before delivery across tasks requiring formal review.

Does subagent code review require specific dependencies or components?

Subagent code review does not require specific dependencies or components. It operates by dispatching a reviewer subagent and requires baseline and head commit SHAs to compare changes effectively.

Why should I use a standardized template for code reviews?

Use a standardized template for code reviews to enforce structured feedback and assess completed work against requirements consistently. This standardization prevents defects from cascading into later stages.