requesting-code-review

Dispatch a code-reviewer subagent to assess code changes between SHAs.

1.5k|69|Updated Mar 13, 2025
One-click install
npx skills add https://github.com/UniClipboard/UniClipboard --skill requesting-code-review-uniclipboard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/UniClipboard/UniClipboard/tree/main/.claude/skills/requesting-code-review
Command: npx skills add https://github.com/UniClipboard/UniClipboard --skill requesting-code-review-uniclipboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates rigorous code reviews by dispatching a dedicated code-reviewer subagent to catch issues early and standardize feedback.

Core Features & Use Cases

  • Dispatch a code-reviewer subagent after each task in subagent-driven development to validate changes
  • Provide BASE_SHA, HEAD_SHA, and a clear PLAN_OR_REQUIREMENTS so reviewers can assess scope and impact
  • Collect and act on feedback to guide subsequent development steps and ensure readiness for merge

Quick Start

Set BASE_SHA and HEAD_SHA to the relevant commits and dispatch the code-reviewer subagent to perform a structured review.

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 for a pull request using a subagent?▼

Automate code review by dispatching a code-reviewer subagent with clear implementation details, base SHA, head SHA, and a defined plan. The reviewer then assesses code quality, architecture, testing, and production readiness to provide structured feedback.

What do I need to provide to run an AI-assisted code review before a merge?▼

To run an AI-assisted code review, you must provide the BASE_SHA and HEAD_SHA of the relevant commits along with a clear PLAN_OR_REQUIREMENTS document so the reviewer can accurately assess scope and impact.

When should I use a code-reviewer subagent in task-driven development?▼

Use a code-reviewer subagent after completing each task in subagent-driven development, during major feature implementations, and for pre-merge checks to catch issues early and standardize feedback.

Does automated code review work without a defined plan or requirements?▼

Automated code review requires a defined plan or requirements. Without clear implementation details and base and head SHAs, the reviewer cannot properly assess code quality, architecture, testing, or production readiness.

What is the best way to standardize feedback across multiple pull requests?▼

Standardize pull request feedback by dispatching a dedicated code-reviewer subagent to evaluate each changeset against a defined plan. This ensures consistent assessment of code quality, architecture, and production readiness.