Skill Detail

Review agent-authored diffs in terminal with herdr-reviewr

Open a terminal review pane beside a coding agent, inspect changed files, add line comments, and send structured review notes back to the agent without leaving the terminal.

Code Quality & ReviewMulti-Framework
Code Quality & Review Multi-Framework Security Reviewed
⭐ 825 GitHub stars
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill review-agent-authored-diffs-in-terminal-with-herdr-reviewr Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
At a glance
Tools required
herdr 0.7.5 or newer, git, macOS or Linux terminal, and optional authenticated gh, glab, or az CLI for PR view
Install & setup
herdr plugin install persiyanov/herdr-reviewr
Author
persiyanov
Publisher
Open Source Project
Last updated
Oct 4, 2026
Quick brief

Use herdr-reviewr when an operator needs to review a coding agent’s worktree before accepting, continuing, or handing off the change. The plugin shows changed files, branch and last-turn diffs, PR context, file contents, search, markdown rendering, line selections, and comments that can be sent back to the agent through herdr.

How it works

What this skill actually does

Invoke this instead of manually reading git diff output when the workflow needs a repeatable terminal review loop for agent-authored changes. The scope boundary is review and feedback on diffs produced by Claude Code, Codex, OpenCode, Pi, or another herdr-managed coding agent. It does not edit the worktree and is not a generic code-review service or PR bot.

Inputs and prerequisites: herdr 0.7.5 or newer, git, macOS or Linux terminal, and optional authenticated gh, glab, or az CLI for PR view.

Setup notes: herdr plugin install persiyanov/herdr-reviewr

Source and verification boundary: use https://github.com/persiyanov/herdr-reviewr as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.