requesting-code-review

Dispatch a code-reviewer subagent for git-range reviews with severity checklists.

5|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/russosalv/NONoise --skill requesting-code-review-russosalv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: requesting-code-review
Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/vendor/superpowers/skills/requesting-code-review
Command: npx skills add https://github.com/russosalv/NONoise --skill requesting-code-review-russosalv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and teams get focused, deterministic code reviews for recent work so defects, missing requirements, and architectural issues are caught before they propagate into later tasks or mainline branches. It separates review context from session history and supplies a clear checklist and verdict format so feedback is actionable.

Core Features & Use Cases

  • Dispatches a dedicated code-reviewer subagent with a concise review context rather than full session history.
  • Git-range based reviews: uses explicit BASE_SHA and HEAD_SHA to produce deterministic diffs for review.
  • Structured checklist and severity categorization: Critical / Important / Minor classifications and a final readiness assessment.
  • Use cases: after each task in subagent-driven development, before merging feature branches, and during batch plan executions.

Quick Start

Dispatch the code-reviewer subagent with BASE_SHA set to the previous commit and HEAD_SHA set to your current commit, include a brief description of what was implemented and a plan or requirements reference.

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 recent git commits before a merge?

Automating code review for recent git commits involves dispatching a subagent with explicit BASE_SHA and HEAD_SHA references to produce a deterministic diff, ensuring focused feedback before merging.

What is the best way to request a code review for a feature branch?

The best way to request a feature branch review is to provide a concise implementation description and requirements reference, isolating the review context from full session history for actionable feedback.

Can I use a checklist to categorize code review severities by Critical, Important, and Minor?

Yes, you can categorize code review severities by applying a structured checklist that classifies issues into Critical, Important, and Minor levels, concluding with a final readiness assessment.

How does deterministic diff inspection work for pull requests?

Deterministic diff inspection for pull requests works by using explicit git base and head SHAs to isolate exact code changes, providing a focused context for the reviewer.

When do I need to run a code review in subagent-driven development?

You need to run a code review in subagent-driven development after completing each task, before merging feature branches, and when validating major changes across a git range.