requesting-code-review

Dispatch a code-reviewer subagent to identify issues between Git commit SHAs.

2|1|Updated Jun 21, 2025
One-click install
npx skills add https://github.com/MeechYourGoals/Chravel --skill requesting-code-review-meechyourgoals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/MeechYourGoals/Chravel/tree/main/.claude/plugins/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/MeechYourGoals/Chravel --skill requesting-code-review-meechyourgoals

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the code review process, ensuring that code is checked for quality, adherence to requirements, and potential issues before being merged, thereby preventing bugs and improving overall code maintainability.

Core Features & Use Cases

  • Automated Review Dispatch: Integrates with a code-reviewer subagent to perform checks.
  • Structured Feedback: Provides clear categories for feedback (Critical, Important, Minor).
  • Workflow Integration: Designed to fit into subagent-driven development, plan execution, and ad-hoc development.
  • Use Case: After completing a new feature, you can use this skill to automatically request a review from the code-reviewer subagent, specifying the changes made and the requirements it fulfills, and then act on the feedback received.

Quick Start

Use the requesting-code-review skill to dispatch the code-reviewer subagent for the latest changes.

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 a Git merge?

To automate code review before a Git merge, dispatch a code-reviewer subagent to identify issues between specified commit SHAs. This verifies changes against requirements and maintains quality before integration.

What is a subagent-driven code review process?

A subagent-driven code review process dispatches an automated reviewer to check code changes against a plan or requirements. It provides structured feedback categorized by severity to ensure adherence to standards before merging.

How do I request a code review for changes between two Git commits?

Request a code review for changes between two Git commits by identifying the base and head commit SHAs and passing them to the review skill. It dispatches a subagent to evaluate the diff and return structured feedback.

Does the code review subagent integrate with CI/CD workflows?

The code review subagent integrates with CI/CD workflows and subagent-driven development by verifying work against plans before merging. It is designed to fit into plan execution and ad-hoc development cycles.

What do I need to identify base and head SHAs for a code review?

To identify base and head SHAs for a code review, you need Git commands to find the specific commit hashes. These SHAs define the boundaries of the code changes the subagent will evaluate for quality and adherence.

How is code review feedback structured and categorized?

Code review feedback is structured into clear categories: Critical, Important, and Minor. This categorization helps developers prioritize issues found in the code changes before the final merge.