reviewr comments
The reviewr sidebar and you share one comment store per worktree. Comments are anchored
to file:start[-end] with a verbatim diff snippet. Find the binary as herdr-reviewr on
PATH (the plugin install links it into ~/.local/bin); if not found, use
$HERDR_PLUGIN_ROOT/bin/herdr-reviewr when that env var is set; otherwise ask the user
for the plugin root. Run every command from the repo you are working in.
Read the user's comments
herdr-reviewr comment list # open comments, human-readable, ids first
herdr-reviewr comment list --json # full documents
Trust the lines snippet over the line number — the code may have moved since the
comment was written. Find the snippet in the file, then act.
The loop
comment list— see what's open.Address each comment in code.
herdr-reviewr comment resolve <id>— mark it done. Do not resolve what you did not address; say so instead.Leave your own notes where you changed or noticed something:
herdr-reviewr comment add --file src/api.rs --start 25 \ --lines '+ await KV.put(key, String(n + 1))' \ --text "KV increments can lose concurrent updates"--author agentis the default; keep it. Notes render as cards in the user's sidebar within a second — no notification step is needed.
Rules
- Never
comment rma user's comment;resolveis yours,rmis theirs. - One comment per finding, at the tightest line range that shows it.
- Keep
--textto a sentence or two; the diff is visible next to the card.