Review Pro banner
tufantunc tufantunc

Review Pro

AI community

Description

Repository-aware AI code review for coding agents — triage → 13 specialist reviewers → synthesis. Reviews what the agent changed and what the repo already knew. Claude Code, opencode, Cursor, Codex.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

review-pro

[![CI](https://github.com/tufantunc/review-pro/actions/workflows/ci.yml/badge.svg)](https://github.com/tufantunc/review-pro/actions/workflows/ci.yml) [![npm version](https://img.shields.io/npm/v/review-pro)](https://www.npmjs.com/package/review-pro) [![website](https://img.shields.io/website?url=https%3A%2F%2Ftufantunc.github.io%2Freview-pro%2F&label=site)](https://tufantunc.github.io/review-pro/) [![license: MIT](https://img.shields.io/github/license/tufantunc/review-pro)](LICENSE) [![node](https://img.shields.io/node/v/review-pro)](https://www.npmjs.com/package/review-pro) [![platforms](https://img.shields.io/badge/platforms-opencode%20%7C%20Cursor%20%7C%20Claude%20Code%20%7C%20Codex-blue)](#install-one-time) [![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/tufantunc/review-pro/badge)](https://scorecard.dev/viewer/?uri=github.com/tufantunc/review-pro)

**The diff is where the change is. The repository is where the evidence is.**

review-pro is an open-source, repository-aware code review system for coding agents — **Claude Code, opencode, Cursor, Codex**. Triage reads the diff and dispatches only the relevant specialists of thirteen; they run in parallel, each required to **locate evidence in the repository** before making a claim; synthesis dedups their findings into one verdict: **BLOCK / REQUEST CHANGES / APPROVE**.

Built for AI-written code — not because agents invent APIs (in [our pre-registered study](studies/2026-08-copilot-pr-pilot) of merged Copilot PRs, they almost never did), but because they write locally plausible code that misses what the repository already knows: the guard added after an incident, the canonical helper, the convention every sibling file follows. That evidence lives in files the diff never touches — so review has to leave the diff.

Sometimes it lives outside the repository. When a change's stated reason cites something specific and external, an upstream issue, a changelog entry, a CVE, the reviewer t