requesting-code-review

Dispatch a code-reviewer subagent to evaluate diffs against requirements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatch a code-reviewer subagent to catch issues before they cascade, ensuring feedback is focused on the work product rather than the developer's session history.

Core Features & Use Cases

  • Automated review trigger: Dispatches a specialized code-review subagent after task completion to validate implementation against requirements.
  • Structured evaluation: Uses a prompt template and git SHAs to generate precise, review-ready assessments that highlight strengths and issues.
  • Workflow integration: Fits into subagent-driven development cycles, including post-task reviews, post-feature reviews, and pre-merge checks.

Quick Start

Request a code review after completing a task to ensure requirements are met before merging.

Frequently Asked Questions about requesting-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is automated code review in a subagent workflow?

Automated code review dispatches a specialized subagent to validate implementation against requirements using git SHAs to generate precise diffs, ensuring feedback focuses on the work product rather than session history.

How do I trigger an automated code review after completing a development task?

To trigger an automated code review, request a review after task completion. The system dispatches a code-reviewer subagent using a structured prompt template and base/head SHAs to generate a review-ready assessment.

When should I run a code review in a subagent-driven development cycle?

Run a code review in a subagent-driven development cycle after each task, after major features, before merging to main, during refactoring, or when stuck, to catch issues before they cascade.

How does the code-reviewer subagent generate a diff for evaluation?

The code-reviewer subagent generates a diff for evaluation by using base and head git SHAs, applying a structured prompt template located at requesting-code-review/code-reviewer.md to produce precise, review-ready assessments.

Can I use this automated code review during refactoring or only before merging?

You can use this automated code review during refactoring and when stuck, not only before merging to main. It fits into subagent-driven development cycles for post-task and post-feature checks.