Agent skill · software engineering · alibaba
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.
Why this skill is useful
Adds specific commands and workflows for delegating code reviews using the OCR CLI, which the AI wouldn't reliably generate on its own.
What it needs
Requires npm installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 19,399 stars on the source repository.
What this skill does
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. Workflow 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 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 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 (mergebase provided in preview output): Commit mode: Workspace mode: Step 4: Review Each File Create a checklist containing every reviewablefiles entry. For each reviewable file: Use (path, status) as the checklist identity. Workspace mode can report the same path twice when a staged deletion is followed by an untracked recreation. 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 4. Mark the file reviewed, or skipped with a concrete reason For large changes, review in bounded batches grouped by shared rules and diff size. Do not stop after finding the first high-severity issue. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills alibaba/open-code-review-delegate--d96708