Show HN: Bobby – Over Engineering PR Reviews

Bobby · a focus-first PR reviewer This is a pull request on GitHub.

Ten files, A to Z, and five threads. Where would you start?

Scroll, and Bobby takes it over, one piece at a time. Same PR, same threads, same review at the end.

InOne bar: where you are in the PR, how far you've got, and the view you're reading in.

InEach file tagged by where it sits: L-1 what the change relies on, L0 the change, L1 what it affects. Tests and generated files stay hidden until you ask.

InBobby's Diff view lays the same diffs out on one canvas, each file right of the files it relies on, so you see the shape of the change before you read a line.

InStep in and one file fills the view: the same diff and threads as GitHub. j k follow the map, from what a change relies on to what it affects.

OutA new tab, to find where it's declared.

In⌘-click a name: its declaration opens over the diff, the whole of it, and esc puts you back where you were.

In⌘⇧-click: every use, in the diff, in the PR's files and elsewhere. Open one to read it in place, or go to it in the diff. One caller the PR never touched still passes no key.

InThe Lens view splits the PR into cores, one idea each, and opens each with a question to keep in mind. With Claude Code installed, Claude names the cores and writes the questions.

InThe code around the change, and how each piece connects, including code the PR never touched. That's where bugs hide.

OutA count of conversations, somewhere below.

InEvery GitHub thread under its line. Your comments wait as drafts; private notes never leave your machine.

Inj k walk the PR in order; a marks a page looked at and moves on. Marks follow the code, so after a force-push only what changed comes back.

Inp parks what's in your head before you switch away. It waits for you in the bar.

InWhere you were, how far you got, and the thought you parked. Progress survives restarts and force-pushes.

OutPinging the author: "who else calls this?"

InSelect some lines, press q, and ask. Claude checks the code around them, and answers right there, on those lines. Ask a follow-up, or start a comment from the answer.

InEach reference Claude makes is checked against the code and opens it: the lines it means, and what the PR changed in them, highlighted.

InTell Claude what to look for, and which of your tools it may read: the ticket in Linear, the doc in Notion, the thread in Slack. It reads the PR file by file, the way you would.

OutA wall of AI comments to wade through.

InThe worst first, each with its code. a adds it to your review, e edits it first, d dismisses it. Nothing is posted unless you add it and submit.

Out"Review changes", at the end of a long page.

Ins posts every draft as one GitHub review: comment, approve or request changes. Private notes stay on your machine.

OutSwitching to the browser to check it landed.

InThe Conversation view is GitHub's own timeline, read live: your approval is already in it, LGTM! and all, next to everyone else's.

Then bobby <pr-url>, or just bobby to pick one. Needs git; Bobby sets up gh. Claude Code is optional: it brings the questions and the reviews.

acme / payments ⌕ Type / to search ＋ ▾◎⇅✉ AB

‹› Code◎ Issues 14⇅ Pull requests 9▷ Actions▦ Projects⛉ Security⌇ Insights⚙ Settings

Retry failed charges safely #482

Edit‹› Code ▾ ⇅ Openmaya wants to merge 2 commits into main from retry-idempotency

Do fees belong in this PR? Happy to review them separately.