persiyanov /herdr-reviewr
Review your agent's diff in a terminal pane and send comments back to Claude Code, Codex, OpenCode or Pi. A herdr plugin.
★ 997⑂ 116👁 0⑃ 99● 73▤ 82
+3
日增长
997
stars
116
forks
0
watchers
99
prs
73
issues
82
releases
README
herdr-reviewr install · quick start · controls · scopes · configuration · limitations · changelog A code-review pane for herdr. Read your agent's diff beside the chat, comment on lines, and send the comments back. !demo - Diff review — the agent's changes, syntax-highlighted. - Unified and split views — one column or side by side, flip with |. - Four diff scopes — uncommitted, branch, last turn, commits. - Last-turn diff — only what the agent's latest turn changed. - Line comments — on a line or a range, sent to the agent in one go. - Text selection — drag to copy, like an editor. - File viewer — any file in the worktree. - Worktree switch — follow your agent into another worktree with W. - Search — files by name and code by content, powered by fff. - Find in file — step through every match. - PR view — the branch's pull request, read-only. - Markdown review — m renders a .md file. - Themes — 20, dark and light. reviewr never edits your files, never sends on its own, and never posts to your PR. Requirements - herdr ≥ 0.9.3 and git. - A terminal with 24-bit color. - macOS, Linux, or Windows. - For the PR tab only: gh, glab, or az (with the azure-devops extension), logged in. Install bash herdr plugin install persiyanov/herdr-reviewr reviewr opens on its own when herdr creates a workspace for a worktree. To open it yourself: bash herdr plugin action invoke open --plugin persiyanov.reviewr To update, reinstall. Your config stays: bash herdr plugin uninstall persiyanov.reviewr && herdr plugin install persiyanov/herdr-reviewr Without herdr, run a release binary on any repo. Everything but Send and the last turn scope works: bash herdr-reviewr ~/some/repo Quick start 1. Pick a file. j / k in the file list, or ] to jump from change to change. 2. Focus the diff. Tab. 3. Select lines. v, then j / k, or drag the line numbers. 4. Comment. c, type, Enter. 5. Send. s puts every comment in the agent's input: the only agent, or the one beside reviewr. S lets you pick. The footer shows the next step, and the worktree you're on at its right. ? lists every key. To toggle reviewr with a key, add this to ~/.config/herdr/config.toml: toml [[keys.command]] key = "cmd+r" many macOS terminals swallow alt+ type = "plugin_action" command = "persiyanov.reviewr.toggle" On Windows, cmd is the Windows key, and Windows takes cmd+r first. Use another key, such as prefix+f. A key for a remote machine goes in that machine's config.toml, because custom commands belong to the server where the panes run. Choose reload config in herdr's menu to apply it. Controls Every key can be rebound (Keybindings). Getting around | Key | Action | | --- | --- | | 1 2 3 | Tab: Changes / All files / PR | | u b t g | Scope: uncommitted / branch / last turn / commits | | B | Pick the base branch | | G | Pick commits | | W | Switch to another worktree of this repo | | j k · ↑ ↓ | Move | | ] | Next / previous change | | f F | Next / previous file | | Page
Top issues
#51Distinguish staged vs unstaged changes in the uncommitted scope3 comments · 2026-08-07#26Allow staging hunks / files directly from reviewr3 comments · 2026-07-20#137Bitbucket Cloud in the PR tab: which transport?2 comments · 2026-10-12#127Windows support: report issues here2 comments · 2026-10-05#47PR tab: send a review comment to the agent2 comments · 2026-08-02#112Add support for go-to-definition1 comments · 2026-09-23#81Bidirectional communication1 comments · 2026-08-24#49Ability to send/comment on pr descriptions akin to current ability to comment on diffs1 comments · 2026-08-04
Discussions
#117Intended to be a OSS project?1 comments · 2026-09-25#69Can i do release my experimental fork of herdr-reviewr plugin for windows?1 comments · 2026-08-16#30Azure DevOps support for the PR tab1 comments · 2026-07-22
Latest release
herdr-reviewr 0.52.2 v0.52.2 2026-11-15Fixed - A markdown file's front matter reads as YAML in both the rendered and the source view, not as a rule over a heading. - Code in rendered markdown wraps at spaces, as the diff does, instead of mid-word.