requesting-code-review

Dispatch a code-review subagent to analyze git range changes before merging.

2|Updated May 13, 2026
One-click install
npx skills add https://github.com/danger-English/claude-code-intro --skill requesting-code-review-danger-english
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/danger-English/claude-code-intro/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/danger-English/claude-code-intro --skill requesting-code-review-danger-english

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to verify work before merging by dispatching a dedicated code-review subagent that analyzes the latest changes against requirements, focusing on the work product rather than private thoughts.

Core Features & Use Cases

  • Early issue detection: A reviewer subagent catches issues after each task or major feature to prevent cascading problems.
  • Context-preserving reviews: The reviewer evaluates the actual output using crafted context, not the session history, preserving your focus for continued work.
  • Templates and integration: Integrates with the Task tool and uses standardized prompts (code-reviewer.md) to ensure consistent feedback.

Quick Start

Request a code review after completing a task by invoking the Task tool with the general-purpose type and the code-reviewer.md 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 automate code review before merging git changes?

Automate code review by dispatching a dedicated code-review subagent with precise git range details and the implementation plan to evaluate work product against requirements before merging.

What is a subagent-based code review workflow?

A subagent-based code review workflow dispatches a dedicated reviewer that analyzes your latest git changes against requirements using crafted context, rather than evaluating your session history.

How do I get early feedback on code to prevent cascading issues?

Get early feedback by initiating a formal code review after each task or significant feature, dispatching a reviewer subagent to catch issues before they cascade into larger problems.

Can I use the Task tool to request a code review for major feature changes?

Yes, request a code review by invoking the Task tool with the general-purpose type and the code-reviewer template to evaluate major feature changes against your plan.

How do I handle feedback from a code review subagent?

Handle code review feedback by fixing critical issues first, addressing important concerns next, and documenting rationale when deviating from the original plan.

Does the code review subagent evaluate my entire session history?

No, the code review subagent evaluates the actual work product output using crafted context, preserving your session focus for continued work rather than reviewing private thoughts.