Sponsor Suno AI Music arrow_forward
Slash Command

OCR: Review

Run an AI-powered multi-agent code review on your changes.

Type
Slash Command
GitHub stars
369
License
Apache-2.0
Repo last updated
Jul 28, 2026

What OCR: Review is

OCR: Review is a slash command published in the spencermarx/open-code-review repository on GitHub, which has about 369 stars. The repository describes itself as: “AI-powered multi-agent code review. Simulates a customizable team of Engineers performing code review with built-in discourse.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

OCR: Review gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install OCR: Review

Claude Code

  1. Download review.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from .ocr/commands/review.md, shared under the repository's Apache-2.0 license. Read the full file on GitHub.

Usage

/ocr-review [target] [--fresh] [--team <ids>] [--reviewer "<description>"]

Arguments

  • target (optional): Branch, commit, or file to review. Defaults to staged changes.
  • --fresh (optional): Clear any existing session for today's date and start from scratch.
  • --team (optional): Replace the default reviewer team for this run. Strict format: reviewer-id:count[,reviewer-id:count...] — the :count is required, each reviewer-id appears once, and ids are lowercase (e.g. principal, martin-fowler). Example: --team principal:2,martin-fowler:1. Forwarded as-is to ocr team resolve --team, which parses and validates it.
  • --reviewer (optional, repeatable): Add an ephemeral reviewer described in natural language. The Tech Lead will synthesize a focused reviewer persona from the description. Does not persist. Example: --reviewer "Focus on error handling in the auth flow".

Examples

/ocr-review                    # Review staged changes
/ocr-review --fresh            # Clear today's session and start fresh
/ocr-review HEAD~3             # Review last 3 commits
/ocr-review feature/auth       # Review branch vs main
/ocr-review src/api/           # Review specific directory
/ocr-review --team principal:2,security:1   # Custom team composition
/ocr-review --reviewer "Review as a junior developer would"
/ocr-review --team principal:1 --reviewer "Focus on error handling" --reviewer "Check accessibility"

Steps

  1. Session State Check (CRITICAL - do this first!)
  2. Load the OCR skill from .ocr/skills/SKILL.md
  3. Execute the 8-phase review workflow defined in .ocr/skills/references/workflow.md
  4. Store results in .ocr/sessions/{date}-{branch}/

Session State Check (Phase 0)

Before starting any review work, you MUST verify the current session state:

Step 1: Check for existing session

# Find today's session directory
ls -la .ocr/sessions/$(date +%Y-%m-%d)-* 2>/dev/null

Step 2: If session exists, verify state

Use ocr state show to read current session state AND verify actual files match (see references/session-files.md for authoritative names):

ocr state show

> Note: Phase completion is derived from filesystem (file existence), not from session state. The current_phase field indicates which phase is active.

Step 3: Determine action

  • If --fresh flag: Delete the session directory and start from Phase 1
  • If session exists and status is closed: Start new round (round-{n+1}) — reuse existing discovered-standards.md and context.md, create new rounds/round-{n+1}/ directory
  • If session exists, status is active, and files match: Resume from current_phase
  • If session exists but state and files mismatch: Report discrepancy and ask user which to trust
  • If no state in SQLite but session files exist: Start new round — use ocr state begin to recreate/resume the session, then start round-{n+1} from Phase 4 (reuse existing standards and context)
  • If no session exists: Start fresh from Phase 1

CRITICAL: Required Artifacts (Must Create In Order)

> See references/session-files.md for the authoritative file manifest.

You MUST create these files sequentially. Do NOT skip to final.md.

.ocr/sessions/{YYYY-MM-DD}-{branch}/
├── discovered-standards.md # Phase 1: merged project standards
├── requirements.md         # Phase 1: user requirements (if provided)
├── context.md              # Phase 2+3: change summary + Tech Lead guidance
└── rounds/
    └── round-1/            # Review round (increments on re-review)
        ├── reviews/
        │   ├── principal-1.md  # Phase 4: reviewer output
        │   ├── principal-2.md  # Phase 4: reviewer output
        │   ├── quality-1.md    # Phase 4: reviewer output
        │   └── quality-2.md    # Phase 4: reviewer output
        ├── discourse.md        # Phase 6: reviewer cross-discussion
        └── final.md            # Phase 7: ONLY after all above exist

State is managed via ocr state CLI commands (stored in SQLite at .ocr/data/ocr.db).

State Management Commands

Prefer the atomic, invariant-checked verbs (v2.0). The CLI enforces the lifecycle — finish refuses to close a workflow whose current round was never finalized, so "completed too soon" cannot happen.

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is OCR: Review?

OCR: Review is a slash command for Claude Code and Claude Cowork from the spencermarx/open-code-review repository on GitHub. Run an AI-powered multi-agent code review on your changes.

How do I install OCR: Review in Claude Code?

Download review.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use OCR: Review in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is OCR: Review safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under Apache-2.0. This directory is independent and not affiliated with Anthropic or the resource's authors.