requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Install
git clone https://github.com/obra/superpowers /tmp/superpowers && ln -s /tmp/superpowers/skills/requesting-code-review ~/.claude/skills/requesting-code-reviewFrom README
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 Before merge to main Optional but valuable: When stuck (fresh perspective) Before refactoring (baseline check) After fixing complex bug How to Request 1. Get git SHAs: 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 {PLANORREQUIREMENTS} - What it should do {BASESHA} - Starting commit {HEADSHA} - Ending commit 3.
More from this repo
systematic-debugging
Used when encountering any bug, test failure, or unexpected behavior, before proposing fixes
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying...
dispatching-parallel-agents
Used when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies