skills/requesting-code-review/SKILL.md
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
npx skillsauth add schlenks/superpowers-bd requesting-code-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Dispatch superpowers-bd:code-reviewer subagent to catch issues before they cascade.
For ad-hoc review outside SDD: /superpowers-bd:cr — interactive flow supporting local changes and GitHub PRs. Supports single or multi-reviewer (N independent reviewers, aggregated, max 10).
Mandatory: After each task in SDD, after completing major feature, before merge to main.
Optional: When stuck, before refactoring, after fixing complex bug.
git rev-parse HEAD~1 for BASE_SHA and git rev-parse HEAD for HEAD_SHAcode-reviewer.md
{PLAN_OR_REQUIREMENTS} -- plan file path, bd show output, or spec{BASE_SHA} / {HEAD_SHA} -- commit rangeFor critical changes, dispatch N=3 independent reviews and aggregate per superpowers-bd:multi-review-aggregation (118% recall improvement per SWR-Bench).
When: Changes >200 lines, security-sensitive, pre-merge to main, complex refactoring.
How: 3 independent code-reviewer subagents with run_in_background: true, each with "You are Reviewer {i} of 3. Review independently." Single review is default for ad-hoc; multi-review is automatic in SDD for max-20x and max-5x tiers.
git log --oneline -10 # find the commit for Task 1, note the SHA
BASE_SHA=<sha-from-above>
HEAD_SHA=<from git rev-parse HEAD>
[Dispatch superpowers-bd:code-reviewer with plan context + SHAs]
[Subagent returns: 4/4 requirements mapped, Important: missing progress indicators]
[Fix -> Continue to next task]
Never:
If reviewer wrong: Push back with technical reasoning, show code/tests, request clarification.
See template at: requesting-code-review/code-reviewer.md
<!-- compressed: 2026-02-11, original: 449 words, compressed: 272 words -->tools
Use when converting a Superpowers-BD implementation plan or Shortcut story into a beads epic with dependency-aware child tasks
development
Use when the user asks for /cr-style review of local changes, commits, a branch diff, or a GitHub PR outside subagent-driven development
development
Use when you have a spec or requirements for a multi-step task, before touching code
tools
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions