Code Review Workspace

Understand a pull request well enough to approve it: agents turn the change into a guided walkthrough and draft the review, and you decide what reaches GitHub.

A BB plugin for reviewing a GitHub pull request or a local Git change. It's for reviewers who need to understand a change before they approve it, often one an agent wrote.

Formerly Guided Review. Coming from it? See Moving from Guided Review.

Quick start · Requirements · Full guide

Agent-drafted comments: severity-tagged drafts with suggested changes, which you edit or remove.

What you can do

Know where to look before you read a line

An agent writes a guide to the change: what it does and why, then chapters in reading order, each with a risk level. The Overview starts you on the lines most likely to hide a defect.

• Start here lists the one to three riskiest lines, each a click from the code.
• Requirements checks what the PR's description and linked issues ask for against the diff: covered, partial, missing, or unclear, with evidence.
• Medium- and high-risk chapters say what to verify. Dig deeper asks the agent for a closer pass over one, then marks each item checked and lists the comments it added.
• Lockfiles, generated files, and diffs over 1,500 changed lines start folded. The reading-time estimate skips lockfiles and generated files.

Chaptered guide: the Overview shows what changed, where to start, requirement coverage and checks.

Start from a drafted review, not a blank page

When the guide is ready, the review agent reviews the change and drafts line comments, a summary, and a suggested verdict. You keep, edit, or remove each one. Nothing posts until you submit, or ask the review agent to post and click Post.

• Each comment has a severity: Blocking, Should fix, Question, or Nit.
• A draft can carry a suggested change. How the agent checked says what it read or ran, with file:line, and stays in BB.
• The automatic review asks for at most 10 comments, each confirmed in the code.
• Problems the PR didn't introduce are marked Pre-existing, and don't count as blocking against Approve.
• Remove an agent's comment with a reason (Wrong, Intended, Already known, or Not worth it), and it won't raise it again unless the code changes.

Comments panel: every draft in one place, by severity, with the agent's evidence.

Get answers about any line without leaving the diff

Ask agent opens the review agent beside the code, in BB's own side panel and chat, as on a thread's page. It can read any file of the review: at the PR's head, at the diff's start, or at the commit you last reviewed.

• Ask about a line, a range, or selected text. The discussion stays under its line, private to you, and never posts.
• On a failing GitHub Actions check, Ask agent quotes the end of its failed log into the agent's box.
• The agent reads the PR's description, linked issues, commits, failing CI, other reviewers' open threads, and the repo's instruction files.

Ask agent: a private question about two lines, answered with file:line evidence.

Post one review, checked before you approve

Finish review shows the summary, the verdict, and exactly what will be posted. Submit to GitHub posts it all as one review.

• The agent suggests a verdict. Only you pick it.
• While you approve, it flags blocking comments, unviewed files in high-risk chapters and flagged files, and, when the agent suggests Approve, files it didn't read, and lists chapters read faster than your pace for code, tests or docs, which a chapter also says as you mark it viewed, until you say it's fine.
• It posts as the GitHub account it verified. If GitHub's answer is lost, it looks for the review it just posted rather than post it twice.
• After you submit, it offers the next review that needs you.

Finish review: you submit one review, with the summary and verdict in view.

See whose turn it is

All reviews sorts every review into Needs review, Waiting on author, Reviewed, and Archive. A push alone never makes a review your turn: authors often push one fix at a time.

• A re-request, a question for you, a mention, or your feedback being handled brings a review back.
• PRs that request your review join the list from GitHub, and so do your own open PRs, with everyone's comments: a teammate's comment waiting for your reply brings yours back as Your PR · 3 new comments; a bot's never does.
• Rows show checks, size, and your feedback's progress, such as 2/5 addressed. Stacked PRs sit together, bottom first.
• Snooze, Pin, and Archive set reviews aside, each with Undo. BB's thread list shows Needs review too.
• Rename… gives a review a name of your own in your lists; its Overview keeps the PR's title under it, and nothing changes on GitHub.
• With the separate Needs You plugin, you get an alert when a guide is ready or a review becomes your turn.
• Other BB plugins, such as a board of tickets, read who each review waits on and whether you've approved it with one call, reviews.v1.status.

All reviews: each row shows whose PR it is, its checks, its size, and its place in a stack.

Re-review only what changed

After new commits, Since your review shows only what changed since the commit you reviewed. The review agent checks your earlier feedback against it before you start.

This is the beginning of the README. Read the rest at the original. Read the full README ↗