Help us improve
Share bugs, ideas, or general feedback.
From ocr
Runs AI-powered multi-agent code review on staged changes, branches, commits, files, or directories. Supports --fresh reset, custom --team composition, and ad-hoc --reviewer personas. Stores results in .ocr/sessions/.
npx claudepluginhub spencermarx/open-code-review --plugin ocrHow this command is triggered — by the user, by Claude, or both
Slash command
/ocr:reviewThe summary Claude sees in its command listing — used to decide when to auto-load this command
**Usage** **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): Override the default reviewer team. Format: `reviewer-id:count,reviewer-id:count`. Example: `--team principal:2,martin-fowler:1`. - `--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 i...
/reviewLaunches a lightweight Review Team to audit current changes with a two-stage review (spec compliance + code quality). Accepts optional file path or commit range; defaults to git diff.
/candid-reviewRuns configurable code review on current changes (staged/unstaged/branch) with harsh/constructive tone and focus areas, categorizes issues with fixes, applies selected ones, supports re-review and git commit.
/reviewRuns OpenCodeReview (OCR) to review code changes and autonomously apply fixes based on comment quality assessment.
/team-reviewOrchestrates a multi-reviewer parallel code review with specialized dimensions (security, performance, architecture, testing, accessibility). Accepts files, directories, git diffs, or PR numbers, and produces a consolidated, severity-organized report.
/reviewDispatches the reviewer agent to review current branch code changes against code quality principles.
/reviewPerforms multi-perspective quality review with consensus gate on staged files or specified path, using presets like content/strategy/code/quick/full.
Share bugs, ideas, or general feedback.
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): Override the default reviewer team. Format: reviewer-id:count,reviewer-id:count. Example: --team principal:2,martin-fowler:1.--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
.ocr/skills/SKILL.md.ocr/skills/references/workflow.md.ocr/sessions/{date}-{branch}/Before starting any review work, you MUST verify the current session state:
# Find today's session directory
ls -la .ocr/sessions/$(date +%Y-%m-%d)-* 2>/dev/null
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
| Phase | Verify file exists |
|---|---|
| context | .ocr/sessions/{id}/discovered-standards.md |
| change-context | .ocr/sessions/{id}/context.md |
| analysis | .ocr/sessions/{id}/context.md (with Tech Lead guidance section) |
| reviews | At least 2 files in .ocr/sessions/{id}/rounds/round-{n}/reviews/ |
| discourse | .ocr/sessions/{id}/rounds/round-{n}/discourse.md |
| synthesis | .ocr/sessions/{id}/rounds/round-{n}/final.md |
Note: Phase completion is derived from filesystem (file existence), not from session state. The
current_phasefield indicates which phase is active.
--fresh flag: Delete the session directory and start from Phase 1closed: Start new round (round-{n+1}) — reuse existing discovered-standards.md and context.md, create new rounds/round-{n+1}/ directoryactive, and files match: Resume from current_phaseocr state init to recreate the session, then start round-{n+1} from Phase 4 (reuse existing standards and context)See
references/session-files.mdfor 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).
| Command | When to Use |
|---|---|
ocr state init --session-id <id> --branch <branch> --workflow-type review --session-dir <path> | Phase 1: Create the session |
ocr state transition --phase <phase> --phase-number <N> [--current-round <N>] | Each phase boundary |
ocr state show | Check current session state |
ocr state close | Phase 8: Close the session |
discovered-standards.md MUST existcontext.md MUST existrounds/round-{n}/reviews/ MUST existrounds/round-{n}/discourse.md MUST existrounds/round-{n}/final.md without completing Phases 1-6The ocr progress CLI reads session state from SQLite for real-time progress display. If you skip phases or don't call ocr state transition, the progress display breaks and users see incorrect state.
Reference
.ocr/skills/SKILL.md for full Tech Lead instructions.ocr/skills/references/workflow.md for detailed workflow phases