requesting-code-review

Review git commit ranges for code quality, architecture, and tests.

Updated Feb 23, 2026
One-click install
npx skills add https://github.com/rishikanthc/ml-superpowers --skill requesting-code-review-rishikanthc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/rishikanthc/ml-superpowers/tree/main/skills/requesting-code-review
Command: npx skills add https://github.com/rishikanthc/ml-superpowers --skill requesting-code-review-rishikanthc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured workflow to request focused code reviews for recent commits so regressions, architectural flaws, missing tests, and other issues are caught early and do not cascade across tasks or into main.

Core Features & Use Cases

  • Post-task and pre-merge reviews: Trigger reviews after every subagent-driven task, after major features, or before merging to main.
  • Git-range based comparison: Use BASE_SHA and HEAD_SHA to scope the diff that the reviewer examines.
  • Structured reviewer template: Enforces checks for code quality, architecture, testing, requirements alignment, and categorizes findings as Critical, Important, or Minor with a clear merge assessment.
  • Use case: When finishing Task 2 in a plan, dispatch the code-reviewer subagent with the commit range and a description so issues are found and fixed before Task 3 begins.

Quick Start

Dispatch the code-reviewer subagent with BASE_SHA and HEAD_SHA filled into the template and request a review of what was implemented and its adherence to the plan.

Frequently Asked Questions about requesting-code-review

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

FAQPage Schema
How do I request a code review for recent git commits before merging?

To request a code review, dispatch the code-reviewer subagent with a specified BASE_SHA and HEAD_SHA git range to scope the diff, along with a description of what was implemented to check for regressions and architectural flaws.

What is the best way to automate pre-merge code quality checks for a pull request?

Pre-merge code quality checks are automated by applying a structured review template that examines git commit ranges, categorizing findings by severity as Critical, Important, or Minor, and providing a clear ready-to-merge verdict.

When should I run a code review in a subagent-driven task workflow?

You should run a code review after completing each subagent-driven task, following major feature implementations, or before merging branches to ensure issues are caught early and do not cascade into subsequent tasks or main.

How does a structured code review template evaluate code quality and architecture?

A structured code review template evaluates code quality and architecture by enforcing checks for testing adherence, requirements alignment, and overall design, categorizing any identified issues by severity to guide the merge assessment.

Can I scope a code review to a specific commit range using git SHAs?

Yes, you can scope a code review to a specific commit range by providing the BASE_SHA and HEAD_SHA values, which limits the diff the reviewer examines to only recent commits within that specified range.