requesting-code-review
Requesting Code Review
Dispatch superpowers-bd:code-reviewer subagent to catch issues before they cascade.
Quick Access
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).
When to Request Review
Mandatory: After each task in SDD, after completing major feature, before merge to main.
Optional: When stuck, before refactoring, after fixing complex bug.
How to Request
- Get git SHAs: run
git rev-parse HEAD~1for BASE_SHA andgit rev-parse HEADfor HEAD_SHA - Dispatch code-reviewer subagent using template at
code-reviewer.md{PLAN_OR_REQUIREMENTS}-- plan file path, bd show output, or spec
More from schlenks/superpowers-bd
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
10writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
9dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
9brainstorming
Use when starting any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
8epic-verifier
Use when all implementation tasks in an epic are closed, before calling finishing-a-development-branch
8rule-of-five-tests
Use when writing 50+ lines of test code, adding test suites, or before claiming test work complete - apply 5 focused passes (Draft, Coverage, Independence, Speed, Maintainability) to catch issues single-shot generation misses
8