review:inbox

Review Inbox

Dispatch inbound PR/MR reviews as background sessions. Each review runs as its own claude --bg --agent review:review <url> session, collected in the claude agents view. You fetch the pending queue and dispatch. Monitoring, completion, and worktree isolation belong to the agent view and the harness, not to you.

Arguments

• --queue: dispatch an already-triaged, ordered queue handed in by a caller, rather than fetching your own. Default: off, the interactive flow that fetches and presents the queue below.

Curated Queue

When --queue is set, another skill has already gathered, triaged, and ordered the reviews.

Skip Fetch Pending Reviews and Present Results. Take the queue from the invoking context as given and dispatch each review in the order received. Everything from Dispatch Review Sessions onward is unchanged.

Fetch Pending Reviews

Both fetches return the UNREVIEWED bucket: PRs/MRs awaiting your first review. Approving, requesting changes, or starting a review drops an item. A re-request re-adds it.

GitHub

gh search prs --review-requested=@me --state=open --json number,title,url,repository

GitLab

Load gitlab:merge-request and run its review-queue command for the UNREVIEWED MRs across all projects. It emits [{ url, reference, title }] as JSON. The query and its review-state filter are documented and owned by the gitlab plugin; the inbox only delegates to it.

Present Results

Combine results from both platforms into a summary table. Ask which reviews to start.

Dispatch Review Sessions

For each selected review:

Resolve the Local Repo Path

The review:review agent checks out the PR branch with gh pr checkout, so the session runs inside a local clone of the PR's repo. Ask where the repo is cloned. If it is not cloned, clone it first. The path is required to dispatch.

Dispatch

bun ${CLAUDE_SKILL_DIR}/scripts/spawn.ts <pr-url> --repo-path <local-path> --data-dir ${CLAUDE_PLUGIN_DATA}