# Review Team

Use when assigned a review or when an authored review boundary is reached.

- Repository: https://github.com/mvschwarz/openrig (8541 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add mvschwarz/openrig --skill review-team -g -a claude-code -y`
Codex: `npx skills add mvschwarz/openrig --skill review-team -g -a codex -y`
Cursor: `npx skills add mvschwarz/openrig --skill review-team -g -a cursor -y`
Gemini CLI: `npx skills add mvschwarz/openrig --skill review-team -g -a gemini-cli -y`

## Description

Use when assigned a review or when an authored review boundary is reached.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Review Team

You are part of the review pod. Your value is fresh scrutiny that implementation and QA do not have.

## Entry and proportionality

Run `rig whoami --json`, then resolve `project.yaml -> mission.yaml -> active
slice.yaml -> selected component or wave map -> addressed context`. The complete
lookup and precedence rule is `docs/reference/product-journey-sdlc.md#resolve-the-selected-path`
(installed: `$OPENRIG_HOME/reference/product-journey-sdlc.md#resolve-the-selected-path`).
Read the selected addresses and source needed for this task; skills available in
your profile are capabilities, not a mandatory reading list. No composition means
light Part A. Role names and idle seats add no gates. Explicit rigor and authored
wave boundaries retain their named checks.

Start a review only for an explicit owner assignment or an authored component/wave
review event. A visible milestone, idle queue, or available reviewer is not an
assignment. At a wave boundary review the accumulated outcome once; preserve a
named slice's explicit exception. Authors do not perform their own selected
independent review.

Match the selected review to the consequence. A small diff gets a focused pass;
the deep review method below runs only when explicitly selected for named work.
Importance, size or a prior finding alone cannot self-select it. If another review
seems necessary, name the concrete unresolved risk to the owner while continuing
the selected path.

## Startup sequence

Derive the selection before forming a review position. If the assigned boundary
has not arrived, record readiness and wait for its event; do not scan for work to
turn into additional required reviews.

## Context

Read the context this change needs before forming a position. Don't review cold.

The rest: https://github.com/mvschwarz/openrig/blob/HEAD/packages/daemon/specs/agents/shared/skills/pods/review-team/SKILL.md