---
title: "Requesting Code Review: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/obra-requesting-code-review/
description: "Prepares a requirements-aware review brief around an explicit base and head revision."
---

# Requesting Code Review: review, setup & limitations · Undominated.ai

> Prepares a requirements-aware review brief around an explicit base and head revision.

[← Explore all skills](/skills/)

DEVELOPMENT WORKFLOW / Superpowers

# Requesting Code Review

Prepares a requirements-aware review brief around an explicit base and head revision.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/obra/superpowers/blob/8ca22dba9a94f28898bbce59f2537ff4d87c747d/skills/requesting-code-review/SKILL.md)

SOURCE REVIEW

 Reviewed 2026-10-07
 Evidence 3 linked sources
 Publisher Superpowers
 Licence [MIT ↗](https://github.com/obra/superpowers/blob/8ca22dba9a94f28898bbce59f2537ff4d87c747d/LICENSE)
 Revision 8ca22dba9a94
 [Read what was—and wasn’t—checked ↓](#review)

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

 [Superpowers · upstream description ↗](https://github.com/obra/superpowers/blob/8ca22dba9a94f28898bbce59f2537ff4d87c747d/skills/requesting-code-review/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Gives the reviewer concrete requirements, implementation context and a bounded Git comparison.
- The companion reviewer template requires file references, severity and rationale and prohibits mutating the reviewed checkout.

### A good fit for

 - Reviewing a committed implementation milestone
- Preparing a focused independent review before integration

### Weigh up before choosing

 - A base-to-head comparison excludes uncommitted changes; include those separately when they are in scope.
- The review is advisory. It does not replace runtime checks or prove production readiness, and read-only instructions require host enforcement.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - Full SKILL.md
- Full code-reviewer.md companion template
- LICENSE

### Our findings

 - The companion forbids moving HEAD or modifying the reviewed checkout and asks for a list of considered-but-unreviewed behavior.

### Not established by this review

 - No end-to-end agent session, effectiveness benchmark or target-project security assessment was run.
- No upstream installer, helper script or generated workload was executed.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/vercel-labs/skills#readme)

DOCUMENTED COMMAND

 npx skills add https://github.com/obra/superpowers/tree/8ca22dba9a94f28898bbce59f2537ff4d87c747d/skills/requesting-code-review --skill requesting-code-review Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - Inspect the pinned skill and its supporting files before installation.
- Run the command from the intended project; use the installer prompts to select the agent and scope.
- Keep the complete skill directory and its licence. Install any task-specific tools separately and test on a small authorized example.

### Before you start

 - Node.js and npm for the Skills CLI
- An Agent Skills compatible coding assistant
- Git history and a host capable of dispatching the reviewer

### Compatibility

Agent Skills compatible clients

### Agent instructions and host-provided tools

 - Read source, Git history and diffs; launch a reviewer through the host
- A separate temporary worktree may be needed to inspect another revision

### Cost model

MIT-licensed instructions; coding-assistant and subagent usage are separate.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Definition at the reviewed revision ↗](https://github.com/obra/superpowers/blob/8ca22dba9a94f28898bbce59f2537ff4d87c747d/skills/requesting-code-review/SKILL.md) Checked 2026-10-07 https://github.com/obra/superpowers/blob/8ca22dba9a94f28898bbce59f2537ff4d87c747d/skills/requesting-code-review/SKILL.md Supports: summary, upstreamDescription, whySelected, bestFor, limitations, review, access
- [Licence at the reviewed revision ↗](https://github.com/obra/superpowers/blob/8ca22dba9a94f28898bbce59f2537ff4d87c747d/LICENSE) Checked 2026-10-07 https://github.com/obra/superpowers/blob/8ca22dba9a94f28898bbce59f2537ff4d87c747d/LICENSE Supports: license, access.cost
- [Skills CLI directory URLs and named-skill selection ↗](https://github.com/vercel-labs/skills#readme) Checked 2026-10-07 https://github.com/vercel-labs/skills#readme Supports: install, compatibility

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Dispatching Parallel Agents ↗ Splits independent investigations into bounded agent assignments and checks their integration afterward.](/skills/obra-dispatching-parallel-agents/)[### API and Interface Design ↗ Designs stable API contracts, consistent errors and retry-safe idempotency behavior.](/skills/addyosmani-api-and-interface-design/)[### Constraint-driven development ↗ Records project quality constraints with measured baselines, enforcement commands and reviewable exceptions.](/skills/addyosmani-constraint-driven-development/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
