PR Buddy for Claude Code

What it does

Three commands, split by whose remarks are on the table.

/pr-buddy:review takes somebody else’s pull or merge request, goes through the diff with you finding by finding, and posts what you kept as a single review. /pr-buddy:respond works the other way round: it triages the threads reviewers left on your own pull request, talks each one through, makes the edits you agree to and drafts the replies. /pr-buddy:check reviews your own branch, uncommitted changes included, and only lists what it finds - it never posts anything. The points you talk it out of are kept as waivers and come back only when the code they relied on changes.

Tests count as part of the change. A feature with no test is a blocking finding, unless the code cannot be tested or a test would take far more setup than it is worth, and every feature let go that way is named with the reason. When the repository has a coverage tool set up, it offers a coverage run of the changed lines first - and when the code is somebody else’s, it says plainly that the run executes their code on your machine.

Nothing goes out unseen

Everything posted lands under your name and notifies people at once; deleting it later does not take the notification back. So every send sits behind one gate. The exact payload is written to files and shown to you in full, never summarized, and it goes out only when your reply is send (or wyślij). “ok”, “looks good” or a question does not count. What goes out is one batch: one review, one notification.

Right before sending, it checks the head of the pull request again. If somebody pushed in the meantime, every comment is anchored to the new diff first and you are told what moved.

The same caution covers the repository. The plugin works on a local clone and runs only read-only git - it never checks out, fetches, commits or pushes, and hands you those commands instead.

In your voice, by your rules

/pr-buddy:learn reads your past review comments and builds two private files: a profile of how you write - length, tone, how you phrase a request or a disagreement - and the rules you keep enforcing. Both live in ~/.claude/pr-buddy/, never in the repository, and the plugin ships no review rules of its own. Where a repository documents its conventions, in CONTRIBUTING.md, AGENTS.md, a linter config or a coverage threshold, the repository’s rule wins.

A drafted comment you would have to rewrite to sound like yourself counts as a failed draft.

What it needs

Claude Code, gh or glab logged in, jq and a POSIX shell - Git Bash on Windows. It works with github.com and gitlab.com; self-hosted GitLab and GitHub Enterprise are not supported. Either platform can be switched off in PR Buddy for Claude Code, for example to keep it away from a work account while that CLI stays logged in. Installing takes two commands, listed in the README.