review-bb-pr

Fetches Bitbucket PR metadata, verifies HEAD, and resolves specification sources for review-pr.

1|1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/williamthorsen/codeassembly --skill review-bb-pr-williamthorsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-bb-pr
Source: https://github.com/williamthorsen/codeassembly/tree/main/packages/agents/content/skills/review-bb-pr
Command: npx skills add https://github.com/williamthorsen/codeassembly --skill review-bb-pr-williamthorsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a Bitbucket pull request requires gathering PR metadata, confirming the local checkout matches the PR head, and assembling specification sources before any review can start. This delegate automates that preparation so the review-pr workflow receives a complete, verified input record. ## Core Features & Use Cases - PR Metadata Fetching: Retrieves PR id, title, description, URL, source and destination branches, and head commit in a single Bitbucket API call. - HEAD Verification: Compares the local HEAD against the PR's head commit using a prefix test and fails closed with a checkout suggestion on mismatch. - Ticket and Spec Resolution: Resolves tickets via override or PR-body parsing (closes/fixes/resolves patterns, Jira-style keys) and builds an ordered spec-source list. - Use Case: A reviewer runs review-pr on a Bitbucket pull request; this delegate returns merge_base_sha, diff_base, spec_sources, and pr_metadata so review-branch can execute the actual review. ## Quick Start Ask the agent to review Bitbucket pull request 42 and it will fetch the PR metadata, verify your checkout, and prepare the specification sources.

Frequently Asked Questions about review-bb-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a Bitbucket pull request with an AI agent?

Invoke review-pr with the PR number or full Bitbucket URL. This delegate fetches the PR metadata, verifies your local HEAD matches the PR head commit, resolves the ticket and spec sources, then hands the inputs to review-branch for the actual review.

How does the skill resolve tickets from a Bitbucket pull request?

It first uses a ticket override if provided, then scans the PR description for patterns like closes #n, fixes #n, resolves #n, bare #n, or Jira-style keys such as MAC-42. If nothing matches, the PR description alone becomes the specification source.

Why does the review stop with a HEAD mismatch error?

The delegate fails closed when the local HEAD does not match the PR's head commit, using a prefix comparison of at least 7 characters. Check out the PR branch with git fetch origin pull-requests/{number}/from:pr-{number} and git checkout pr-{number}, or pull the latest commits.

Does Bitbucket PR review support linked issues like GitHub?

No. Bitbucket Cloud's PR API does not expose a structured closingIssuesReferences field, so this delegate intentionally uses a body-parse cascade instead. The divergence from the GitHub delegate is documented and should not be silently patched.

What is the difference between review-bb-pr and review-branch?

review-bb-pr only prepares inputs: metadata fetching, HEAD verification, diff-base resolution, and spec-source assembly. The actual review logic runs inside review-branch, which review-pr invokes with the resolved-output record.