Skill

bitbucket-pr

Create, view, manage, and merge Bitbucket pull requests using bbt. Use this skill when the user wants to work with pull requests — creating, listing, reviewing, or merging them.

npx claudepluginhub tanyagray/claude --plugin bitbucket

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Use the `bbt` CLI to manage Bitbucket pull requests.

SKILL.md

Similar Skills

skill-lookup

159.9k

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

prompt-lookup

159.9k

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

next-compile

139.2k

Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.

1 file

vercel-next-js-2

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitFeb 26, 2026

Actions

View Source View Plugin View on GitHub View README

Bitbucket Pull Requests

Use the bbt CLI to manage Bitbucket pull requests.

Common Operations

List Pull Requests

# List open pull requests in the current repository
bbt pr list

# List pull requests for a specific repository
bbt pr list -R workspace/repo

View a Pull Request

# View pull request details by ID
bbt pr view <pr-id>

# View for a specific repository
bbt pr view <pr-id> -R workspace/repo

Create a Pull Request

# Interactive creation
bbt pr create

# Create for a specific repository
bbt pr create -R workspace/repo

When creating a PR, bbt will prompt for:

Title: A concise description of the change
Description: Detailed explanation, linked issues, testing notes
Source branch: The branch containing your changes
Destination branch: Usually main or develop
Reviewers: Bitbucket usernames to request review from

Merge a Pull Request

# Merge a pull request by ID
bbt pr merge <pr-id>

# Merge for a specific repository
bbt pr merge <pr-id> -R workspace/repo

Workflow Tips

Use $ARGUMENTS to reference a specific PR ID if the user provides one
Always run bbt pr list first to understand open PRs and their IDs
When creating PRs, suggest a clear title and description that explains why the change is needed
After merging, remind the user to delete the source branch if no longer needed

Pull Request Best Practices

Title format: Use imperative mood — "Add feature X", "Fix bug Y", "Update dependency Z"
Description: Include what changed, why, and how to test it
Reviewers: Tag appropriate team members based on the code changed
Small PRs: Encourage keeping PRs focused and small for faster review cycles

Bitbucket REST API (Advanced)

For operations not yet in bbt, use the Bitbucket REST API directly:

# List PR comments (requires BITBUCKET_TOKEN env var)
curl -s -u "${BITBUCKET_USER}:${BITBUCKET_TOKEN}" \
  "https://api.bitbucket.org/2.0/repositories/{workspace}/{repo}/pullrequests/{id}/comments"

# Approve a PR
curl -s -X POST -u "${BITBUCKET_USER}:${BITBUCKET_TOKEN}" \
  "https://api.bitbucket.org/2.0/repositories/{workspace}/{repo}/pullrequests/{id}/approve"

# Decline a PR
curl -s -X POST -u "${BITBUCKET_USER}:${BITBUCKET_TOKEN}" \
  "https://api.bitbucket.org/2.0/repositories/{workspace}/{repo}/pullrequests/{id}/decline"