Ocr

Skill definitions, reviewer personas, and workflow references that power Open Code Review.

Getting Started

All OCR workflows require the CLI for session state management. Install it first:

# 1. Install the CLI
npm install -g @open-code-review/cli

# 2. Initialize in your project (copies these assets to .ocr/)
cd your-project
ocr init

To update after a package upgrade:

ocr update

This updates skills and workflow references while preserving your .ocr/config.yaml and all reviewer personas (both default and custom).

Via Claude Code Plugin

/plugin marketplace add spencermarx/open-code-review
/plugin install ocr@aclarify

What This Package Contains

agents/
├── skills/ocr/              # The OCR skill
│   ├── SKILL.md             # Tech Lead orchestration logic
│   ├── references/
│   │   ├── workflow.md        # 8-phase review workflow
│   │   ├── session-files.md   # Authoritative file manifest
│   │   ├── session-state.md   # State management
│   │   ├── discourse.md       # Multi-agent debate rules
│   │   ├── final-template.md  # Final review template
│   │   └── reviewers/         # Persona definitions (customizable)
│   │       ├── principal.md     # Architecture, design patterns
│   │       ├── quality.md       # Code style, best practices
│   │       ├── security.md      # Auth, data handling, vulnerabilities
│   │       ├── testing.md       # Coverage, edge cases
│   │       ├── martin-fowler.md # Famous engineer persona
│   │       └── ...              # 28 personas total
│   └── assets/
│       ├── config.yaml        # Default configuration
…

Commands

Why two formats? Windsurf requires flat command files with a prefix (/ocr-command), while Claude Code and Cursor support subdirectories (/ocr:command). Both invoke the same underlying functionality.

Skill Architecture

The SKILL.md file defines the Tech Lead role — the orchestrator that:

1. Discovers project context (config, OpenSpec, reference files)
2. Analyzes changes and identifies risk areas
3. Selects and spawns reviewer personas based on your team configuration
4. Facilitates discourse between reviewers
5. Synthesizes findings into a unified review

Reviewer Personas

28 personas across four tiers:

Famous Engineer personas review through the lens of each engineer's published work and philosophy — e.g., Martin Fowler focuses on refactoring and domain modeling, Kent Beck on test-driven development, Sandi Metz on object-oriented design.

Create custom reviewers via the /ocr:create-reviewer command or by adding .md files to .ocr/skills/references/reviewers/. See the reviewer template.

Ephemeral reviewers can be added per-review with --reviewer — no persistence required. See the review.md command spec for details.

Multi-model teams — assign different models to different reviewers via .ocr/config.yaml. Three forms (shorthand, { count, model }, per-instance list), optional model aliases, and an optional workspace default. See the main README for details.

Map Agent Personas

The /ocr:map command uses specialized agents:

These run with configurable redundancy (default: 2). See .ocr/config.yaml → code-review-map.agents.

Session Structure

.ocr/sessions/{YYYY-MM-DD}-{branch}/
├── discovered-standards.md  # Project context (shared across rounds)
├── context.md               # Change analysis (shared)
└── rounds/
    ├── round-1/
    │   ├── reviews/         # Individual reviewer outputs
    │   │   ├── principal-1.md
    │   │   ├── quality-1.md
    │   │   └── ephemeral-1.md  # From --reviewer (if used)
    │   ├── discourse.md     # Cross-reviewer discussion
    │   └── final.md         # Synthesized review
    └── round-2/             # Created on re-review
├── map/
│   └── runs/
│       └── run-1/
│           ├── map.md           # Code Review Map
│           └── flow-analysis.md # Dependency graph (Mermaid)

Running /ocr-review again on an existing session creates a new round if the previous round is complete. See references/session-files.md for the complete file manifest.

License

Apache-2.0