requesting-code-review

A skill in obra/superpowers · 321,873 stars on GitHub

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Security grade of this SKILL.md: SAFE · how we grade

How to install requesting-code-review

npx skills add obra/superpowers --skill requesting-code-review -a claude-code

The skills CLI copies this one skill into Claude Code (use -a for another agent). Or read its SKILL.md on GitHub.

What the SKILL.md says

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. 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. 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. {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.

Other skills in obra/superpowers

  • brainstorming You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning…
  • diagnosing-superpowers Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results,…
  • dispatching-parallel-agents Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
  • executing-plans Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, o…
  • finishing-a-development-branch Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
  • receiving-code-review Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable…
  • subagent-driven-development Use when executing implementation plans with independent tasks in the current session
  • systematic-debugging Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
  • test-driven-development Use when implementing any feature or bugfix, before writing implementation code
  • using-git-worktrees Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated w…
  • using-superpowers Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clari…
  • verification-before-completion Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and…
  • writing-plans Use when you have a spec or requirements for a multi-step task, before touching code
  • writing-skills Use when creating new skills, editing existing skills, or verifying skills work before deployment