revdiff CLI
A CLI opens diffs and documents in a terminal so a person can annotate lines and pass feedback to a coding agent
- 945 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The tool reads code and saves annotation history
- The plugin passes feedback to a model that can propose or apply edits under client permissions
Install
- Works in
Manual install
brew install umputun/apps/revdiffPrepared terminal tool for macOS and Linux.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The tool reads code and saves annotation history
- The plugin passes feedback to a model that can propose or apply edits under client permissions
This is third-party code. Review the repository files before installing.
What it does
revdiff opens code changes in a terminal interface and accepts line annotations. A file tree sits beside the diff and context. On exit it prints annotations for a coding agent or another consumer. It also reviews complete files or standard input. Word-level highlighting and hunk navigation help inspect changes. Other modes show tracked files or selected paths. Claude Code and Codex integrations open a review beside the agent session. The user leaves comments, which the agent processes afterward. Feedback retains its file and line references.
Who it is for. Code and documentation reviewers sending an agent comments tied to specific lines.
Good fit when
- Annotate questionable lines after a change and return feedback to the same agent
- Review an entire plan or document without another editor
- Inspect a pull-request patch not checked out locally
- Recover saved annotations after an interrupted interactive review
Not a fit when
- You need defects found without a human reviewer
- The environment cannot open a supported interactive terminal
- You need feedback posted to GitHub automatically without another integration
Example request
Open the current branch changes in revdiff for my annotations. After I exit, list the comments and propose fixes without changing code before agreement.Limitations
Revision comparison needs Git, Mercurial or Jujutsu; plain-file review does not, while the Jujutsu blame gutter needs 0.27 or later. Source builds require Go 1.26, but prebuilt binaries do not. Agent plugins need a supported terminal such as tmux, kitty or WezTerm, with launch behavior varying by terminal. Exiting with annotations saves history in ~/.config/revdiff/history/ that may contain code; inspect comments before passing them to a model.
How to disable. Close the review interface and disable any installed agent plugin. Remove the CLI through its package manager. Review saved annotations and history separately; disabling the tool does not delete them.
FAQ
How do I review staged changes?
Run `revdiff --staged` in the repository. Use a range such as `revdiff HEAD~1 HEAD` for two revisions. Confirm the intended scope first.
How do I review one Markdown file?
Use `revdiff --only README.md`, replacing the path. This works outside a repository and provides heading navigation for Markdown.
What format do annotations use?
Text records identify a file, line and change type in a header, followed by the comment. Save them for an agent or parse them with another script.
How do I ask for an explanation only?
Include `??` in the annotation. Plugins classify it as a question and answer it first. Other comments can remain change requests.
Does exit code 10 mean failure?
Not when `--exit-code-on-annotations` is enabled: it reports annotations. Plugins treat it as a successful feedback handoff. This exit-code behavior is off by default.
What license does revdiff use?
MIT.
Discussion
No questions or reviews yet.
Related
CLI toolsA code-review CLI and plugin for agents: reads a git diff and writes line-level comments with context
The CLI matches linter diagnostics to code changes and reports findings locally or through an approved review channel.
A skill and CLI for code review: a team of reviewer agents inspects changes independently, debates findings and produces one report
A CLI that opens a local git diff in the browser like GitHub's Files changed tab; comments copy out as prompts for an agent
A CLI turns Git changes into a guided code walkthrough with questions and explanations written by your existing agent
code-preview.nvim: review agent edits in Neovim
code-preview.nvim
A Neovim plugin: edits from Claude Code, OpenCode, Copilot CLI and Codex CLI open as a native diff before they hit disk
README in short
A separate plugin reviews completed plans and is installed independently of diff review. Local configuration controls themes, wrapping and keys.