---
description: Review local changes against Harness repository rules and docs.
---

# /review

## Preflight

- Read `/AGENTS.md`, `/docs/ARCHITECTURE.md`, `/docs/HARNESS.md`, `/docs/ADR.md`, and `/docs/UI_GUIDE.md` if they exist.
- Identify the changed files or generated `phases/` artifacts that need review.
- If the user wants a delegated review, use the read-only custom agent `harness_reviewer` only when they explicitly asked for subagents.

## Plan

- State what evidence will be checked: docs, changed files, generated phase files, and validation output if available.
- Prioritize correctness, architecture drift, missing Sprint Contracts, CRITICAL rule violations, and missing tests over style commentary.

## Commands

- Invoke `$harness-review`.
- Use Codex built-in `/review` when the user specifically wants a code-review style pass over the working tree or git diff.
- If validation is relevant, run `python scripts/validate_workspace.py` or explain why it was not run.

## Verification

- Confirm that every finding is tied to a file and an actual rule or behavioral risk.
- If no findings remain, say so explicitly and mention residual risks or missing evidence.

## Summary

## Result
- **Action**: reviewed Harness changes
- **Status**: success | partial | failed
- **Details**: findings, docs checked, and validation status

## Next Steps

- Suggest the smallest follow-up: fix the top finding, rerun validation, or execute a pending phase.
