PR Review Comments
When a feature opens a pull request, people review it on GitHub. Shep reads those review comments and can address them for you: an agent changes the code in the feature’s worktree, pushes to the same branch, and replies on each comment with what it changed, an answer to the question, or why it disagrees.
This works for features waiting for review: stopped at the merge gate with an open pull request.
Ask on GitHub with #shep
Write #shep anywhere in a review comment:
#shep rename
totaltototalCents, it holds cents
Shep checks open pull requests for new comments every two minutes. Once the agent is done, the change is pushed and the comment gets a reply like:
Renamed to
totalCentsin refund-order.ts and its tests.Changed in c0ffee1.
Checking needs Shep running in the background: shep start (or shep ui). The background daemon also tracks merges, closes and CI results of the pull requests.
Address comments yourself
shep feat comments <id> # the PR's comments and what happened to each
shep feat address-comments <id> # address every pending comment
shep feat address-comments <id> <comment-id> # only these (ids from `shep feat comments`)Both commands read the latest comments from GitHub first; --no-refresh uses the ones Shep already has. address-comments works whatever the space setting below says, and without the daemon running.
Each comment has a status: Pending, Addressing, Addressed (changed or answered, and replied to), Declined (the agent disagreed and replied why) or Failed.
In the web UI, open the feature’s Merge Review tab. Under the diff, Review comments lists the comments by kind (On a line, Conversation, Review) with their status and a link to GitHub. Address N pending starts a round, and the list updates when it ends with what the last round pushed.
What a round does
- The agent gets the pending comments (up to 20 per round) in the feature’s worktree, with the file, line and diff around inline comments.
- Where a comment asks for a change, it changes the code, runs the tests around it, commits, and pushes the feature branch. It never force-pushes or rebases.
- Shep replies to each comment: in the review thread for inline comments, or as a new comment quoting the original for conversation and review comments. A reply for a code change names the commit.
If the agent leaves changes uncommitted or unpushed, Shep commits them as fix: address review comments and pushes them itself.
If the change can’t be pushed, nothing is replied and the comments are marked Failed. Fix the branch and run the round again; failed comments are picked up again. A round has a 30-minute limit, and only one runs per feature at a time.
Choose which comments Shep answers on its own
Which comments Shep addresses without being asked is a setting of the feature’s space:
| Setting | Shep addresses on its own |
|---|---|
mention (default) | Comments that contain #shep |
all | Every new review comment |
off | Nothing; you start each round with address-comments or the web button |
shep space config <space> --pr-comments all
shep space config <space> --resolve-threads # resolve a thread after changing code for it
shep space config <space> --no-resolve-threads # leave threads for the reviewer (default)In the web UI: Spaces, then Agent settings on the space’s card.
Changing these settings needs Spaces, behind the spaces feature flag (on by default; see Spaces). Every repository belongs to a space, the default one if you never created another, so #shep mentions and shep feat address-comments work without setting anything up.
A round runs as the space’s accounts: its GitHub login and git identity, like the feature’s own runs. The fallback commit-and-push described above uses your machine’s own git setup instead.
Things to know
- Shep never answers itself. Each reply carries an invisible marker, so Shep skips its own replies, even though
ghposts them from your account. - Bots are skipped. Comments from GitHub apps and bots are ignored.
- Resolved threads count as addressed. A comment in a thread that is already resolved isn’t picked up.
- Only features waiting for review. A feature that is still implementing, or whose PR is merged or closed, has no comments to address.