Add plugin entries: code-review, pr-manager

[robennals]

Two plugins from https://github.com/robennals/bb-plugins, one entry each.

What they do

Code Review — lists the pull requests awaiting your review, filtered by whether the request came to you personally, to one of your teams, or to anyone. Reviewing one spawns a BB thread that runs your own configured review skills over the change and reports structured findings. Each finding arrives with its background, the problem, a suggested fix and a ready-to-post comment, shown next to the code it refers to; you edit and post them individually. Nothing reaches GitHub until you press post, and comments join an in-progress GitHub review when you have one open.

PR Manager — shows your own open pull requests and recent merges with CI and review state summarised as waiting, failing, feedback, approved or merged, and opens or links the BB worktree thread for the one you pick.

GitHub only

Both plugins are GitHub-specific and have no support for any other forge. They shell out to the GitHub CLI for everything: there is no abstraction over GitLab, Bitbucket, Gitea, or plain git remotes, and pointing either at a non-GitHub repository does not degrade — it fails.

The two differ in how tightly they are bound:

• Code Review pins github.com. It probes gh auth status --hostname github.com, and it builds https://github.com/... links for pull request diffs and file permalinks. GitHub Enterprise will not work without changes.
• PR Manager does not pin a hostname. It calls gh without --hostname and takes URLs from the API, so it would likely follow a GH_HOST configured for GitHub Enterprise — but that is untested and not a claim I would make for it.

Both descriptions say "GitHub" so this is visible in the store, not only here.

Source

Both track semver ranges against the same public repository, with per-plugin tag prefixes:

Entry	Subdir	Range	Latest tag
code-review	plugins/code-review	^0.1.0	code-review/v0.1.0
pr-manager	plugins/pr-manager	^0.1.0	pr-manager/v0.1.1

All tags are annotated. code-review/v0.1.0 and pr-manager/v0.1.0 point at 1655ce9e17ad0d533dd0cf02a61a93371fd6213f; pr-manager/v0.1.1 points at 83d0e8f.

Plugin checks

Run at the tagged commits:

• code-review — tsc --noEmit clean, 232 tests pass, bb plugin build produces dist/server.js and dist/app.js.
• pr-manager — tsc --noEmit clean, 5 tests pass, bb plugin build produces app and host artifacts.

Both install and run against BB 0.40.

Marketplace checks

• npm ci --ignore-scripts, npm run build — composes 84 entries.
• npm run check — both entries resolve their tags at the public repository. The two failures it reports (taskboard, usage-tracker) are pre-existing npm liveness failures in other entries and are untouched by this branch.
• Icons are vendored into icons/ with content-hashed filenames, single-colour SVG so BB's currentColor mask follows the user's theme. Both were checked at 14, 16, 20 and 64 px in light and dark.

Things a reviewer should know

• Both plugins shell out to gh and inherit whatever the user's GitHub CLI is authenticated for. Neither stores a token; there is no other network access.
• Code Review writes to GitHub only on an explicit per-comment action, and only ever as a review comment or pull request comment. It never approves, requests changes, or submits a review. It refuses to post a comment whose line is outside the diff, offering a file-level or pull request comment instead.
• Code Review spawns BB threads to run reviews, and registers a bb code-review CLI command that those threads use to read the fetched pull request and submit findings. Review agents are told not to run gh, not to post, and not to modify the checkout.
• PR Manager ships a bb.host entry so it can create worktrees and threads on a connected machine.
• Neither plugin declares an agent provider, contributes instructions, or reads other plugins' data.

[SawyerHood]

Automated note from a Claude Code agent, posted on behalf of the marketplace maintainer.

Reviewed and merged. We security-reviewed the source at the exact tag your entry resolves to, installed it from that entry into a dev build of BB 0.40, and confirmed it loads and runs. Thanks for the submission — nice work.