Source profileQuality 84/100Review permissions

alibaba/open-code-review/skills/open-code-review-delegate/SKILL.md

open-code-review-delegate

Delegation mode for open-code-review (OCR). Instead of OCR calling an LLM endpoint, this skill instructs the host agent to perform the code review itself, using OCR only for deterministic engineering: file selection and rule resolution. Use when the host agent should drive the review with its own LLM capabilities.

Source repository stars
18,669
Declared platforms
0
Static risk flags
2
Last source update
2026-08-04
Source checked
2026-08-04

Decision brief

What it does—and where it fits

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.

Best for

  • Use when the host agent should drive the review with its own LLM capabilities.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/alibaba/open-code-review --skill "skills/open-code-review-delegate"
Safe inspection promptEditorial

Inspect the Agent Skill "open-code-review-delegate" from https://github.com/alibaba/open-code-review/blob/6dc3eb067071c01e7234ac6032a9f7d656a29f84/skills/open-code-review-delegate/SKILL.md at commit 6dc3eb067071c01e7234ac6032a9f7d656a29f84. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

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

    mode (workspace / range / commit)from / to / commit / mergebase — ref metadata for constructing git commandsReviewable file list — paths, status, insertions/deletions
  2. 02

    Step 1: Preview — Determine What to Review

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

    mode (workspace / range / commit)from / to / commit / mergebase — ref metadata for constructing git commandsReviewable file list — paths, status, insertions/deletions
  3. 03

    Step 2: Get Rules for Files

    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.

    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.
  4. 04

    Step 3: Get Diffs

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

    Use git directly based on the mode/ref info from Step 1:Range mode (mergebase provided in preview output):
  5. 05

    Step 4: Review Each File

    For each reviewable file:

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

Permission review

Static risk signals and limitations

Runs scripts

medium · line 15

The documentation asks the agent to run terminal commands or scripts.

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

Runs scripts

medium · line 56

The documentation asks the agent to run terminal commands or scripts.

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

Reads files

low · line 68

The documentation asks the agent to read local files, directories, or repositories.

# New untracked files — read directly (entire file is new code)

Reads files

low · line 135

The documentation asks the agent to read local files, directories, or repositories.

**Untracked files in workspace mode** — `preview` includes untracked files. For these, read the file directly instead of using `git diff`.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score84/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars18,669SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
alibaba/open-code-review
Skill path
skills/open-code-review-delegate/SKILL.md
Commit
6dc3eb067071c01e7234ac6032a9f7d656a29f84
License
Apache-2.0
Collected
2026-08-04
Default branch
main
View the original SKILL.md

Open Code Review — Delegation Mode

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:

ScenarioCommand
Workspace changesocr delegate preview
Branch comparisonocr delegate preview --from main --to feature
Single commitocr 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:

FieldTypeRequiredDescription
pathstringyesRelative file path
contentstringyesReview comment describing the issue
start_lineintegernoStart line in the new file
end_lineintegernoEnd line in the new file
categoryenumnobug, security, performance, maintainability, test, style, documentation, other
severityenumnocritical, 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

CommandPurpose
ocr delegate previewWhich files to review + mode/ref metadata
ocr delegate rule <path...>Review rules grouped by content

Shared Flags

FlagDescription
--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 mattersocr delegate operates on the Git repo at the current directory. Use --repo /path to override.
  • Untracked files in workspace modepreview 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.

Alternatives

Compare before choosing