Requesting code review

Skill tspry/superpowers-devops/skills/requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirementsFrom its SKILL.md

Install

npx -y skills add tspry/superpowers-devops --skill requesting-code-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.6 KB, as published. Nobody here has run it

Requesting Code Review

Dispatch a code reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation — never your session's history.

Core principle: Review early, review often.

When to Request Review

Mandatory:

After each task in subagent-driven development
After completing major feature or infra change
Before merge to main

Optional but valuable:

When stuck (fresh perspective)
Before refactoring (baseline check)
After fixing complex bug or config issue

How to Request

1. Get git SHAs:

BASE_SHA=$(git rev-parse HEAD~1)  # or origin/main
HEAD_SHA=$(git rev-parse HEAD)

2. Dispatch code reviewer subagent — dispatch a general-purpose subagent, filling the template at code-reviewer.md.

Placeholders:

{DESCRIPTION} — Brief summary of what you built
{PLAN_OR_REQUIREMENTS} — What it should do
{BASE_SHA} — Starting commit
{HEAD_SHA} — Ending commit

3. Act on feedback:

Fix Critical issues immediately
Fix Important issues before proceeding
Note Minor issues for later
Push back if reviewer is wrong (with reasoning)

Red Flags

Never:

Skip review because "it's simple"
Ignore Critical issues
Proceed with unfixed Important issues

If reviewer is wrong: Push back with technical reasoning and show evidence.

See template at: code-reviewer.md