review git:20260809.a4882b4A

Immutable. This exact content is served forever at /api/v1/blob/8017b36b226d3eba.

---
name: review
description: Top-level, user-facing code-review workflow for verified issues in specific files, functions, diffs, or code sections. Use when the user directly requests a review and may need to adjudicate its findings. Do not use as an orchestrator for a delegated leaf review or finding-validation task.
---

# Code Review

## Leaf-mode guard

If the task identifies your role as `leaf-reviewer` or sets
`delegation-budget: 0`, read and follow
[`references/single-pass.md`](./references/single-pass.md), complete one review
yourself, return the report to the caller, and stop.

## Run the review

Read and follow [`references/single-pass.md`](./references/single-pass.md), then
[`references/orchestration.md`](./references/orchestration.md). The latter's
user-facing response rules replace the former's leaf return behavior.

## Adapting for your project

- **Name your standards explicitly** in
  [`references/single-pass.md`](./references/single-pass.md) — `AGENTS.md`,
  optional `CLAUDE.md`, `docs/DESIGN-PRINCIPLES.md` — in place of the generic
  "relevant design documents".
- **Add project-specific "what to look for" items** to the same file, e.g. "new
  public APIs have rate limiting", "DB queries use parameterized inputs", "error
  messages don't leak internal paths".
- **Tune the exclusion list** there if your team *does* want style or refactor
  feedback. The default is strict because noise is the bigger problem.