Tool

Review Code Changes with AI-Powered Line-Level Feedback

Open Code Review (ocr) is Alibaba's AI code review CLI, trading some recall for high precision at about 1/9 the tokens of a general agent.

Works with gitgithubnpmanthropicclaude

91
Spark score
out of 100
Updated last month
Source checked Aug 21, 2026
Version 1.9.8

Add to Favorites

Why it matters

Automatically review Git diffs and pull requests with an AI agent that provides structured, line-level code feedback by reading full file contents, searching the codebase for context, and applying fine-grained review rules to catch defects before they ship.

Outcomes

What it gets done

01

Analyze staged, unstaged, or branch-range Git diffs to identify files requiring review

02

Bundle related files together and run parallel sub-agent reviews with isolated context

03

Generate precise, line-level code comments using LLM tool-calling with codebase search

04

Position and reflect on review comments to ensure location accuracy and content quality

Source

Get it from source

A command-line tool. Install it with its own package manager. Spark does not host a copy of it.

Open source
  1. 1

    Install the CLI globally. (README)

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

    Configure an LLM provider and model (interactive). (README)

    ocr config provider ocr config model

Check that it works:

cd your-project ocr review

Requires: Git >= 2.41, Node.js with npm, An LLM provider API key, unless you use Delegation Mode

Reports

Agent outcome reports

No reports yet

Overview

Open Code Review

Open Code Review is an AI-powered code review CLI, originally Alibaba's internal tool, that reads Git diffs and produces structured, line-level review comments using an agent with codebase search and tool-use access. It splits work between deterministic engineering for file selection and rule matching and an LLM agent for dynamic review decisions. Use it when a general-purpose coding agent's code review has shown incomplete coverage, drifting line references, or inconsistent quality on large changesets. Not the right choice if maximum recall matters more than precision, or if you want your own agent's LLM to run the review via Delegation Mode instead.

What it does

Open Code Review (ocr) is an AI-powered code review CLI that originated as Alibaba's internal review assistant - after two years serving tens of thousands of developers and catching millions of defects internally, it was open-sourced. It reads a Git diff, sends changed files to a configurable LLM through an agent with tool-use access, and produces structured, line-level review comments; the agent can read full file contents, search the codebase, and inspect other changed files for context rather than reviewing a diff in isolation. ocr scan extends the same engine to review whole files with no diff at all, for auditing an unfamiliar codebase.

When to use - and when NOT to

Use it when general-purpose coding agents doing code review, Claude Code with Skills, for example, have shown the pain points OCR was built to fix: incomplete coverage on large changesets, line numbers and file references drifting from the actual issue, and review quality that fluctuates with small prompt changes. On a benchmark of 200 real pull requests across 50 open-source repositories and 10 languages, cross-validated by 80+ senior engineers against 1,505 annotated ground-truth issues, OCR scored higher Precision and F1 than a general-purpose agent on the same underlying model while using about 1/9 the tokens - at the deliberate cost of lower Recall, favoring fewer false alarms over catching every possible issue. It is not the right tool if you want maximum recall over precision, or if you'd rather have your own coding agent's LLM do the reviewing entirely - that's what Delegation Mode is for.

Inputs and outputs

ocr review covers workspace changes - staged, unstaged, untracked; ocr review --from main --to feature-branch reviews a branch's changes since it diverged, in merge-base mode; ocr review --commit <sha> reviews one commit; any of these can resume from ocr session list after an interruption. ocr scan [--path <dir>] reviews whole files instead of a diff, with no git history required. In Delegation Mode (ocr delegate preview, ocr delegate rule <files>), your own coding agent runs the review using its own LLM - OCR only handles file selection and rule resolution, so no separate OCR API key is needed.

Integrations

The core design splits work between deterministic engineering and the agent: hard-constrained steps - which files need review, bundling related files like paired message_en.properties/message_zh.properties into isolated-context sub-agent units for large-changeset stability and concurrency, and template-based rule matching per file - are handled by engineering logic rather than the model, while the agent handles dynamic decisions through scenario-tuned prompts and a toolset distilled from analyzing real production tool-call traces. It integrates with Claude Code, Codex, Cursor, OpenCode, and Skill-compatible agents as plugins, an MCP server for extending the review agent with external tools, CI/CD platforms including GitHub Actions, GitLab CI, GitFlic CI, and Gerrit, and OpenTelemetry for observability.

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

Requires Git 2.41+, runs on Windows, macOS, and Linux, and is Apache-2.0 licensed.

Who it's for

Teams whose general-purpose AI code review has been inconsistent or unreliable on large changesets, who want a CLI that trades some recall for high-precision, line-accurate findings, either self-managed or delegated to their own coding agent.

Source README
OpenCodeReview logo

OpenCodeReview

alibaba%2Fopen-code-review | Trendshift alibaba%2Fopen-code-review | Trendshift

npm Build status License Ask DeepWiki OpenSSF Best Practices

Windows macOS Linux Claude Code Codex Cursor

English | 简体中文 | 日本語 | 한국어 | Русский


What is Open Code Review?

Open Code Review is an AI-powered code review CLI tool. It originated as Alibaba Group's internal official AI code review assistant - over the past two years, it has served tens of thousands of developers and identified millions of code defects. After thorough validation at massive scale, we incubated it into an open source project for the community. Simply configure a model endpoint to get started.

It reads Git diffs, sends changed files to a configurable LLM via an agent with tool-use capabilities, and generates structured review comments with line-level precision. The agent can read full file contents, search the codebase, inspect other changed files for context, and produce deep reviews - not just surface-level diff feedback. Beyond diff review, ocr scan reviews entire files for auditing unfamiliar codebases or directories that have no meaningful diff.

Visit the official website for more details.

Benchmark

Compared to general-purpose agents (Claude Code), Open Code Review achieves significantly higher Precision and F1 with the same underlying model, while consuming only ~1/9 of the tokens and completing reviews faster. Note that its Recall is lower than general-purpose agents - a deliberate trade-off favoring precision over noise.

A real-world code review benchmark built from 50 popular open-source repositories, 200 real Pull Requests, and 10 programming languages - cross-validated by 80+ senior engineers (1,505 annotated ground-truth issues).

Hugging Face Explore the AACR-Bench dataset on Hugging Face.

Metric What it measures Why it matters
F1 Harmonic mean of precision and recall Best single number for overall review quality
Precision Proportion of reported issues that are real defects Higher = fewer false alarms to triage
Recall Proportion of real defects that are found Higher = fewer issues slip through review
Avg Time Wall-clock time per review Matters for CI pipeline latency
Avg Token Total tokens consumed per review Directly impacts API cost

Why Open Code Review?

The Problem with General-Purpose Agents

If you've used general-purpose agents like Claude Code with Skills for code review, you've likely encountered these pain points:

  • Incomplete coverage - On larger changesets, agents tend to "cut corners," selectively reviewing only some files and missing others.
  • Position drift - Reported issues frequently don't match the actual code location, with line numbers or file references drifting off target.
  • Unstable quality - Natural-language-driven Skills are hard to debug, and review quality fluctuates significantly with minor prompt variations.

The root cause: a purely language-driven architecture lacks hard constraints on the review process.

Core Design: Deterministic Engineering × Agent Hybrid

Open Code Review's core philosophy is to combine deterministic engineering with an agent, each handling what it does best.

Deterministic Engineering - Hard Constraints

For review steps that must not go wrong, engineering logic - not the language model - guarantees correctness:

  • Precise file selection - Determines exactly which files need review and which should be filtered, ensuring no important change is missed.
  • Smart file bundling - Groups related files into a single review unit (e.g., message_en.properties and message_zh.properties are bundled together). Each bundle runs as a sub-agent with isolated context - a divide-and-conquer strategy that stays stable on very large changesets and naturally supports concurrent review.
  • Fine-grained rule matching - Matches review rules to each file's characteristics, keeping the model's attention sharply focused and eliminating information noise at the source. Compared to purely language-driven rule guidance, template-engine-based rule matching is more stable and predictable.
  • External positioning and reflection modules - Independent comment-positioning and comment-reflection modules systematically improve both the location accuracy and content accuracy of AI feedback.

Agent - Dynamic Decision-Making

The agent's strengths are concentrated where they matter most - dynamic decisions and dynamic context retrieval:

  • Scenario-tuned prompts - Prompt templates deeply optimized for code review, improving effectiveness while reducing token consumption.
  • Scenario-tuned toolset - Distilled from deep analysis of tool-call traces in large-scale production data - including call frequency distributions, per-tool repetition rates, and the impact of new tools on the overall call chain - resulting in a purpose-built toolset that is more stable and predictable for code review than a generic agent toolkit.

How to Use

Prerequisites

  • Git >= 2.41 - Open Code Review relies on Git for diff generation, code search, and repository operations.

CLI

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

After installation, the ocr command is available globally.

For other installation methods (install script, GitHub Release binary, from source), see Installation.

Quick Start

1. Configure LLM

You must configure an LLM before reviewing code, unless you use Delegation Mode.

ocr config provider          # Select a built-in provider or add a custom one
ocr config model             # Pick a model for the active provider

The interactive UI guides you through provider selection, API key entry, and model configuration, then automatically tests connectivity.

For CLI setup, environment variables, custom providers, and other advanced configuration, see Configuration.

2. Review

cd your-project

# Workspace mode — review all staged, unstaged, and untracked changes
ocr review

# Branch range — reviews feature-branch's changes since it diverged from main (merge-base mode)
ocr review --from main --to feature-branch

# Single commit
ocr review --commit abc123

# Resume an interrupted range or commit review
ocr session list
ocr review --from main --to feature-branch --resume <session-id>

# Full-file scan — review whole files instead of a diff (no git history needed)
ocr scan                          # scan the entire repository
ocr scan --path internal/agent    # scan a directory or specific files
ocr scan --resume <session-id>   # resume an interrupted full-file scan

# Delegation mode — let your AI coding agent perform the review itself
# OCR handles file selection and rule resolution; no LLM configuration needed
ocr delegate preview
ocr delegate rule src/main.go src/handler.go

Documentation

Full documentation lives at open-codereview.ai/docs:

  • Quickstart - install and run your first review
  • Installation - all platforms and package managers
  • CLI Reference - every command and flag
  • Review Rules - customize review rules with path filtering and targeting
  • Configuration - config keys and environment variables
  • MCP Server - extend the review agent with external tools
  • Coding Agent Integrations - choose the platform you use
    • Claude Code - install a plugin with review slash commands
    • Codex - install a plugin with callable review skills
    • Cursor - install a plugin with portable review skills
    • OpenCode - install native review tools and slash commands
    • QCA Forward - run delegation mode with the QCA host model and a ready-to-publish template
    • Skill-compatible agents - install the portable agent skill
  • Review Execution Modes - after integration, choose which LLM performs the review
  • CI/CD Integration - GitHub Actions, GitLab CI, GitFlic CI, and Gerrit integration
  • Session Viewer - browse and replay review sessions in browser
  • Telemetry - OpenTelemetry integration for observability
  • FAQ - common questions and troubleshooting

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.