requesting-code-review

Requesting Code Review - Code Review Request Skill

Skill Overview

requesting-code-review is a Claude Code skill used to verify that work meets requirements before completing tasks, implementing major functionality, or merging code. It does this by dispatching code review sub-agents to catch and fix issues early.

Use Cases

1. Sub-agent–Driven Development

In a sub-agent–driven development workflow, after each task is completed, requesting a code review helps identify and fix problems before they accumulate. This early intervention ensures code quality and prevents subsequent tasks from building on faulty foundations.

2. After Major Feature Development Is Complete

Once the main functionality is implemented, a comprehensive code review is necessary. This can confirm whether the code satisfies requirements and the plan, ensure feature completeness and correctness, and prepare for subsequent testing and deployment.

3. Before Merging into the Main Branch

Code review before merging into the main branch is mandatory. This is the final quality gate to ensure the code about to enter the main branch complies with team standards and does not introduce breaking changes or known issues.

Core Capabilities

Code Review Dispatch

The requesting-code-review skill can dispatch the superpowers:code-reviewer sub-agent to perform code reviews. By providing the base SHA, head SHA, and an implementation description, the system compares code changes and generates a detailed review report, including strengths analysis and issue categorization (Critical, Important, Minor).

Workflow Integration

This skill supports integration into multiple development workflows: reviewing after each task in sub-agent–driven development, reviewing after each batch of tasks when executing plans, and pre-merge reviews during ad-hoc development. It can also request reviews when difficulties arise to gain a new perspective and establish a baseline check before refactoring.

Handling Review Feedback

The skill provides clear guidance for processing review feedback: Critical issues must be fixed immediately, Important issues must be addressed before proceeding, and Minor issues can be logged for later follow-up. If the reviewer is mistaken, developers can refute using technical reasoning and request clarification.

Common Questions

What is the requesting-code-review skill?

requesting-code-review is a Claude Code skill that helps developers request code reviews at the right time. It follows the core principles of “early review, frequent review.” By dispatching the code-reviewer sub-agent, it can uncover potential issues in the code to ensure code quality and project stability.

How do I use requesting-code-review to perform a code review?

First obtain the Git SHA values (base SHA and head SHA). Then use the Task tool to dispatch a superpowers:code-reviewer sub-agent, filling in a template that includes implementation details, planned requirements, SHA values, and descriptions. After the review is complete, take appropriate actions based on the priority levels of the issues in the feedback.

When should I request a code review?

Code review is mandatory in the following cases: after each task in sub-agent–driven development, after completing the main functionality, and before merging into the main branch. Optional but valuable cases include: when you encounter difficulties and need a new perspective, establishing a baseline before refactoring, or after fixing complex bugs. Do not skip reviews, even if the task seems simple.