How it works
Autonomous code review that never uploads your repository. The full technical description of rev-local — what it does, what it is made of, and what state it is in.
The premise
rev-local watches repositories already on your disk, reviews each new change with a coding CLI you already have installed, and publishes the findings back to wherever the work lives — a pull request, an issue tracker, a wiki.
Everything runs locally. The repository is never uploaded and the review engine is a process you control. It supports git, GitHub and Subversion, and a review can never mutate the repository under review.
What is included
git, GitHub and Subversion discovery with copy-on-review materialisation
Full pipeline: depth selection, diff truncation, finding normalisation, fingerprinting and dedupe
Process supervision with an environment denylist that keeps credentials out of the review process
SQLite store with an audit log and a budget ledger; MCP client over stdio and streamable HTTP
How it is built
rev-local is built on Rust, SQLite, MCP, Claude Code and Codex.
The repository is 93% Rust, 5% TypeScript by volume — a description of what the work actually consists of rather than what it is filed under.
It carries 76 commits since Aug 2026, most recently changed in Aug 2026.
The method behind it
Every project here starts as a written specification, and the specification stays authoritative once code exists. The repository keeps a build plan with live status, an append-only decision log recording where the implementation departed from the plan, and a handoff document describing the true current state — including the parts that are not finished.
That is why a portfolio this wide is not a shallow one, and it is why this page can describe the product without overstating it.
Current state
In development. Under active work right now.
The source is public. Read it rather than taking this page for it.
Next
Put rev-local in your pipeline
Ask about integrating it with the repositories and agents you already run.