Do I need an API key to use this Bitbucket automation skill?

No, API keys are not required. The skill uses OAuth via `RUBE_MANAGE_CONNECTIONS` with the Bitbucket toolkit, so you authenticate through Rube MCP instead of managing Bitbucket app passwords or API tokens directly.

What are the five main workflows this skill covers?

The skill covers pull request management (create, list, inspect, diff), repository and workspace administration (list/create/delete repos, list members), issue tracking (create, update, comment, delete), branch operations (list, create from commit hash), and PR code review (fetch diff, post comments).

Why do I need to call RUBE_SEARCH_TOOLS before using this skill?

You should call `RUBE_SEARCH_TOOLS` first to get current tool schemas because Composio's tool definitions can change, ensuring you're working with the latest parameter formats and available operations.

What's the difference between creating and updating an issue in terms of assignee fields?

When creating an issue, you pass an `assignee` username, but when updating an issue, you must use `assignee_account_id` (a UUID) instead — these are different fields for the same concept.

Should destructive operations like deleting a repository be run automatically?

No, destructive calls like `BITBUCKET_DELETE_REPOSITORY` and `BITBUCKET_DELETE_ISSUE` should always be confirmed with the user first rather than run autonomously, since they are irreversible.

Skill

Automate Bitbucket Repository and PR Management

Name: Bitbucket Automation via Rube MCP
Availability: OnlineOnly
Author: Antigravity

Automate Bitbucket repos, PRs, branches, and issues through Rube MCP's Composio toolkit - no API keys, OAuth-based connection.

Get skill

Works with bitbucket

Antigravity

Own this? Claim it

Spark score

out of 100

Updated 10 days ago

Version 15.7.0

Models

universal

Add to Favorites

Why it matters

Streamline your Bitbucket operations by automating repository management, pull request workflows, issue tracking, and branch management using the Composio Bitbucket toolkit.

Outcomes

What it gets done

Manage pull requests, including creation, review, and inspection.

Automate repository and workspace administration tasks.

Track and manage Bitbucket issues and comments.

Automate branch creation and listing.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-bitbucket-automation | bash

Overview

Bitbucket Automation via Rube MCP

A tool-sequence guide for automating Bitbucket pull requests, repositories, issues, and branches through Rube MCP's Composio toolkit, including OAuth setup and documented parameter pitfalls. Use when an agent needs to manage Bitbucket PRs, issues, branches, or repositories programmatically, confirming with the user before any delete operation.

What it does

This skill drives Bitbucket through Rube MCP (https://rube.app/mcp), which exposes Composio's Bitbucket toolkit as MCP tools - no API keys required, just OAuth via RUBE_MANAGE_CONNECTIONS with toolkit bitbucket. It covers five workflows end to end: pull request management (create, list, inspect, diff, and diffstat a PR), repository and workspace administration (list/create/delete repositories, list workspace members), issue tracking (create, update, comment on, and delete issues), branch operations (list branches, create from a commit hash), and PR code review (fetch a diff, then post top-level or inline threaded comments).

When to use - and when NOT to

Use this skill whenever a task needs to touch Bitbucket programmatically - opening or reviewing a PR, triaging issues, managing branches, or auditing repositories across a workspace - through an agent rather than the Bitbucket UI. Every workflow assumes the Bitbucket connection is already ACTIVE (checked via RUBE_MANAGE_CONNECTIONS) and that RUBE_SEARCH_TOOLS is called first to get current tool schemas, since Composio's tool definitions can change. Destructive calls - BITBUCKET_DELETE_REPOSITORY (irreversible, does not remove forks) and BITBUCKET_DELETE_ISSUE (permanent) - should always be confirmed with the user first rather than run autonomously.

Inputs and outputs

Every call is scoped by workspace and repo_slug, resolved up front via BITBUCKET_LIST_WORKSPACES and BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE rather than guessed. PR creation takes source_branch, an optional destination_branch (defaults to the repo's actual main branch, which may not literally be main), and reviewers as an array of {"uuid": "{...}"} objects, not usernames - UUIDs must include curly braces. Issue creation takes title, content, kind (bug/enhancement/proposal/task), and priority (trivial through blocker); notably CREATE_ISSUE takes an assignee username while UPDATE_ISSUE takes an assignee_account_id UUID - different fields for the same concept. List endpoints support Bitbucket Query Language (BBQL, e.g. name~"api" AND is_private=true, string values must be double-quoted) and page-based pagination (page/pagelen, default 10, up to 50 for PRs and 100 elsewhere) - always paginate fully rather than trusting the default page size. Diff-fetching tools (GET_PULL_REQUEST_DIFF) accept max_chars to truncate large diffs before they overwhelm context.

# Rube MCP endpoint - add as an MCP server, no API key needed
https://rube.app/mcp

Integrations

Built on Composio's Bitbucket toolkit surfaced through Rube MCP's tool-discovery layer (RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS), which handles Bitbucket OAuth so the calling agent never touches Bitbucket app passwords or API tokens directly.

Who it's for

Agents and developers automating Bitbucket workflows - reviewing and commenting on pull requests, triaging and updating issues, creating branches from a specific commit, or auditing repositories across a workspace - who want a documented tool sequence and known parameter pitfalls (ID formats, BBQL quoting, inconsistent field names between create/update calls) rather than rediscovering them from Composio's raw tool schemas each time.

FAQ

Common questions

Discussion