requesting-code-review

Dispatch a code-reviewer subagent to review changes before merging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates early quality assurance by dispatching a code-reviewer subagent to review changes before merging.

Core Features & Use Cases

  • Dispatch the code-reviewer subagent after completing tasks to catch issues before they cascade.
  • Provide structured feedback with severity levels and clear remediation guidance.
  • Integrate with standard PR workflows to gate merges and improve code quality.
  • Use Case: After finishing Task 2, invoke the skill to generate a review for the new authentication module.

Quick Start

Trigger the review after completing a task by invoking this skill to dispatch the code-reviewer subagent, then review the feedback and apply fixes.

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 pull request merge?

Automated code reviews before a pull request merge are handled by dispatching a code-reviewer subagent to evaluate changes, enforce structured feedback, and verify production readiness. It applies to post-implementation reviews of major features within CI/CD workflows.

What is a subagent-driven code review workflow?

A subagent-driven code review workflow dispatches an automated code-reviewer subagent to evaluate changes after a task is completed. It enforces structured feedback, severity-based issue categorization, and production-readiness checks through a templated review process.

How do I enforce production-readiness checks in my CI/CD pipeline?

Production-readiness checks in a CI/CD pipeline are enforced by dispatching a code-reviewer subagent to review changes pre-merge. This automated process applies a templated review to evaluate major features and categorize issues by severity.

Can I integrate automated severity-based issue categorization into my development tasks?

Integrating automated severity-based issue categorization into development tasks is supported by dispatching a code-reviewer subagent post-implementation. It applies a templated review process to generate structured feedback with clear remediation guidance.

When do I need to run an automated code review?

Automated code reviews are needed after completing subagent-driven development tasks or before merging major features. Running a review at these stages catches issues early, enforces structured feedback, and verifies production readiness before changes cascade.

Does the code-review subagent work without external dependencies?

The code-review subagent operates without external dependencies, dispatching a templated review process to analyze changes. It categorizes issues by severity and provides structured remediation guidance independently within your workflow.