Open code review delegate

Open Code Review — Delegation Mode

This Codex plugin skill intentionally mirrors the canonical skill at skills/open-code-review-delegate/SKILL.md. Keep both files synchronized when updating OCR delegation instructions; a symlink is avoided because plugin installs may only materialize the plugin subtree.

A skill for performing AI code review where OCR provides deterministic engineering (file filtering, rule resolution) and the host agent performs the actual review using its own intelligence and tools.

Prerequisites

which ocr || echo "NOT INSTALLED"

If ocr is not installed:

npm install -g @alibaba-group/open-code-review

No LLM configuration is needed for delegation mode.

Workflow

Step 1: Preview — Determine What to Review

ocr delegate preview [--from <ref> --to <ref>] [--commit <hash>] [--exclude <patterns>]

This outputs:

• mode (workspace / range / commit)
• from / to / commit / merge_base — ref metadata for constructing git commands
• Reviewable file list — paths, status, insertions/deletions
• Excluded files — with exclusion reason

Common invocations:

Scenario	Command
Workspace changes	ocr delegate preview
Branch comparison	ocr delegate preview --from main --to feature
Single commit	ocr delegate preview -c abc123

Step 2: Get Rules for Files

ocr delegate rule <path1> <path2> ...

Pass the reviewable file paths from Step 1. Output is grouped by rule content — files sharing the same rule appear under one group, avoiding repetition.

Step 3: Get Diffs

Use git directly based on the mode/ref info from Step 1:

Range mode (merge_base provided in preview output):

git diff <merge_base>..<to> -- <path>

Commit mode:

git show <commit> -- <path>

Workspace mode:

# Tracked files
git diff HEAD -- <path>
# New untracked files — read directly (entire file is new code)
cat <path>

Step 4: Review Each File

For each reviewable file:

1. Get its diff (Step 3)
2. Consult its Rule Group (from Step 2) for the review checklist
3. Conduct a thorough review, using appropriate context tools as needed

Step 5: Format Output

Each comment must follow this structure:

Field	Type	Required	Description
path	string	yes	Relative file path
content	string	yes	Review comment describing the issue
start_line	integer	no	Start line in the new file
end_line	integer	no	End line in the new file
category	enum	no	bug, security, performance, maintainability, test, style, documentation, other
severity	enum	no	critical, high, medium, low

Step 6: Classify and Report

Group findings by severity:

• Critical/High: Bugs, security issues, data loss risks — always report
• Medium: Performance concerns, error handling gaps, maintainability issues — report with context
• Low: Style nits, minor suggestions — report only if clearly valuable

Discard likely false positives silently.

Step 7: Fix (Optional)

If the user requested "review and fix":

• Apply High/Critical fixes directly
• Describe Medium fixes that require manual intervention
• Skip Low-priority items unless trivial

Sub-commands Reference

Command	Purpose
ocr delegate preview	Which files to review + mode/ref metadata
ocr delegate rule <path...>	Review rules grouped by content

Shared Flags

Flag	Description
--from <ref>	Source ref for range mode
--to <ref>	Target ref for range mode
-c, --commit <hash>	Single commit mode
--repo <path>	Repository root (default: cwd)
--rule <path>	Custom rule.json path
--exclude <patterns>	Comma-separated exclude patterns
-b, --background <text>	Business context
-B, --background-file <path>	Business context from Markdown file

Gotchas

• No LLM needed on OCR side — delegation mode never calls an LLM. All intelligence comes from the host agent.
• Rules are grouped — Files sharing the same rule are grouped together in the output. You can pass any number of paths per call; for large changes, fetch rules per-batch as you review.
• Working directory matters — ocr delegate operates on the Git repo at the current directory. Use --repo /path to override.
• Untracked files in workspace mode — preview includes untracked files. For these, read the file directly instead of using git diff.
• Background context — pass --background to preview when you have requirement context; it appears in the output for your reference during review.