Bitbucket#

Work with Bitbucket from chat — browse repositories, inspect files, manage branches, review pull requests, and coordinate repository workflows via the Bitbucket Cloud API with OAuth authentication.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Bitbucket API access yourself.

Setup in 3 Steps#

Step 1: InstallStep 2: Pair AccountStep 3: Connect Bitbucket_App-specific connection GIF coming soon_Run the install command in OpenClawSign in and approve the deviceOpen the dashboard and connect Bitbucket

How It Works#

text

┌─────────────────┐     ┌──────────────┐     ┌──────────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│ Bitbucket Cloud API  │
│   (User Chat)   │     │   (OAuth)    │     │ (Repos/PRs/Branches)│
└─────────────────┘     └──────────────┘     └──────────────────────┘
         │                       │                       │
         │  1. Install Plugin    │                       │
         │  2. Pair Device       │                       │
         │  3. Connect Bitbucket  │                       │
         │                       │  4. Secure Token      │
         │                       │  5. Proxy Requests    │
         │                       │                       │
         ▼                       ▼                       ▼
   ┌──────────┐           ┌──────────┐           ┌──────────┐
   │  SKILL   │           │ Dashboard│           │ Bitbucket│
   │  File    │           │ Auth     │           │ Cloud │
   └──────────┘           └──────────┘           └──────────┘

Install#

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

bash

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Bitbucket again."

Quick Start#

bash

# List repositories in a workspace
clawlink_call_tool --tool "bitbucket_list_repositories_in_workspace" --params '{"workspace": "your-workspace"}'

# List branches in a repository
clawlink_call_tool --tool "bitbucket_list_branches" --params '{"workspace": "your-workspace", "repo_slug": "your-repo"}'

# Get a pull request
clawlink_call_tool --tool "bitbucket_get_pull_request" --params '{"workspace": "your-workspace", "repo_slug": "your-repo", "pull_request_id": 1}'

Authentication#

All Bitbucket tool calls are authenticated automatically by ClawLink using the user's connected Bitbucket account.

No API key is required in chat. ClawLink stores the OAuth token securely and injects it into every Bitbucket API request on the user's behalf.

Getting Connected#

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=bitbucket and connect Bitbucket.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management#

List Connections#

bash

clawlink_list_integrations

Response: Returns all connected integrations. Look for bitbucket in the list.

Verify Connection#

bash

clawlink_list_tools --integration bitbucket

Response: Returns the live tool catalog for Bitbucket.

Reconnect#

If Bitbucket tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=bitbucket
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration bitbucket

Security& Permissions#

• Access is scoped to repositories and resources accessible to the connected Bitbucket account.
• All write operations require explicit user confirmation. Before executing any create, update, or delete call, confirm the target resource and intended effect with the user.
• Destructive actions (delete repository, delete branch, delete issue) are marked as high-impact and must be confirmed.
• Repository deletion does not affect forks.

Tool Reference#

Repository Operations#

ToolDescriptionModebitbucket_list_repositories_in_workspaceList repositories in a workspaceReadbitbucket_list_repositoriesList public repositoriesReadbitbucket_get_repositoryGet repository metadataReadbitbucket_create_repositoryCreate a new repository in a workspaceWritebitbucket_delete_repositoryPermanently delete a repositoryWritebitbucket_browse_repository_pathGet file content or list directory at a revisionReadbitbucket_get_file_from_repositoryGet a specific file's content at a commitReadbitbucket_list_repository_pathsList files and directories under a pathRead

Branch Operations#

ToolDescriptionModebitbucket_list_branchesList branches with optional name filteringReadbitbucket_get_branchGet branch metadata and target commitReadbitbucket_create_branchCreate a new branch from a target commitWritebitbucket_get_repositories_branching_modelGet the repository's branch workflow configurationReadbitbucket_get_repositories_effective_branching_modelGet effective branching model (including inheritance)Read

Commit Operations#

ToolDescriptionModebitbucket_list_commitsList commits with optional branch/path filtersReadbitbucket_get_repositories_commitGet detailed commit informationReadbitbucket_get_commit_diffGet the unified diff for a commit or rangeReadbitbucket_get_commit_changesGet changed files in a commitReadbitbucket_get_commit_build_statusGet build status for a commitReadbitbucket_get_commit_diffstatGet diffstat (files changed, lines added/removed)Read

Pull Request Operations#

ToolDescriptionModebitbucket_list_pull_requestsList pull requests by state (OPEN/MERGED/DECLINED)Readbitbucket_get_pull_requestGet a single pull request with full detailsReadbitbucket_get_pull_request_commitsGet commits included in a PRReadbitbucket_get_pull_request_diffGet the unified diff for a PRReadbitbucket_get_pull_request_diffstatGet diffstat for a PRReadbitbucket_create_pull_requestCreate a new pull requestWritebitbucket_update_pull_requestUpdate PR title, description, or reviewersWritebitbucket_merge_pull_requestMerge a pull requestWritebitbucket_approve_pull_requestApprove a pull requestWritebitbucket_request_pull_request_changesRequest changes on a PRWritebitbucket_create_pull_request_commentAdd a top-level or threaded comment to a PRWritebitbucket_delete_pull_request_commentDelete a PR commentWritebitbucket_resolve_pull_request_commentResolve or reopen a PR comment threadWrite

Issue Operations#

ToolDescriptionModebitbucket_list_issuesList issues with optional state/priority filtersReadbitbucket_create_issueCreate a new issueWritebitbucket_update_issueUpdate issue attributesWritebitbucket_delete_issuePermanently delete an issueWritebitbucket_create_issue_commentAdd a comment to an issueWrite

User & Workspace#

ToolDescriptionModebitbucket_get_current_userGet the authenticated user's profileReadbitbucket_list_workspacesList workspaces accessible to the userReadbitbucket_get_workspaceGet workspace metadataReadbitbucket_list_workspace_membersList members of a workspaceReadbitbucket_list_workspace_projectsList projects in a workspaceRead

Pipelines & Deployments#

ToolDescriptionModebitbucket_list_pipelinesList pipeline runs for a repositoryReadbitbucket_get_repositories_pipelines2Get a specific pipeline's detailsReadbitbucket_list_repositories_environmentsList deployment environmentsReadbitbucket_list_deploymentsList deployment historyRead

Code Search#

ToolDescriptionModebitbucket_get_workspaces_search_codeSearch code across all repos in a workspaceReadbitbucket_search_user_repositories_codeSearch code in a specific user's reposRead

Code Examples#

List branches in a repository#

bash

clawlink_call_tool --tool "bitbucket_list_branches" \
  --params '{
    "workspace": "your-workspace",
    "repo_slug": "your-repo",
    "q": "name~\"feature\""
  }'

Create a pull request#

bash

clawlink_call_tool --tool "bitbucket_create_pull_request" \
  --params '{
    "workspace": "your-workspace",
    "repo_slug": "your-repo",
    "title": "Add new feature",
    "source_branch": "feature/new-feature",
    "destination_branch": "main",
    "description": "This PR adds the new feature as described in issue #123"
  }'

Approve a pull request#

bash

clawlink_call_tool --tool "bitbucket_approve_pull_request" \
  --params '{
    "workspace": "your-workspace",
    "repo_slug": "your-repo",
    "pull_request_id": 42
  }'

Get file content from a repository#

bash

clawlink_call_tool --tool "bitbucket_get_file_from_repository" \
  --params '{
    "workspace": "your-workspace",
    "repo_slug": "your-repo",
    "path": "README.md",
    "commit_revision": "main"
  }'

Discovery Workflow#

1. Call clawlink_list_integrations to confirm Bitbucket is connected.
2. Call clawlink_list_tools --integration bitbucket to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration bitbucket.
5. If no Bitbucket tools appear, direct the user to https://claw-link.dev/dashboard?add=bitbucket.

Execution Workflow#

text

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → search → describe → call                      │
│                                                             │
│  Example: List repos → List branches → Show results          │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                     │
│  list → get → describe → preview → confirm → call         │
│                                                             │
│  Example: Describe tool → Preview changes → User approves   │
│           → Execute update                                 │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer read, list, search, and get operations before writes when that reduces ambiguity.
4. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Notes#

• Branch names must be unique within a repository and must not include the refs/heads/ prefix.
• Pull request IDs are numeric. Use bitbucket_list_pull_requests to find PR IDs.
• Repository deletion does not affect forks — forks are separate copies.
• Pagination: use the next field in responses to iterate through large result sets.
• BBQL (Bitbucket Query Language) supports server-side filtering for branch names.

Error Handling#

Status / ErrorMeaningTool not foundThe tool name does not exist in the current catalog. Verify with clawlink_list_tools --integration bitbucket.Missing connectionBitbucket is not connected. Direct the user to https://claw-link.dev/dashboard?add=bitbucket.BranchNotFoundBranch does not exist. Check the branch name.PullRequestNotFoundPull request does not exist. Check the PR ID.RepositoryNotFoundRepository does not exist or is not accessible.InvalidArgumentInvalid parameter or missing required field. Review the tool schema with clawlink_describe_tool.Write rejectedUser did not confirm a write action. Always confirm before executing writes.

Troubleshooting: Tools Not Visible#

1. Check that the ClawLink plugin is installed: bash

   openclaw plugins list
   
   

2. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.

3. If a fresh chat does not help, run: bash

   openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
   openclaw gateway restart
   
   

4. After restart, tell the user to send /new again and retry.

Troubleshooting: Invalid Tool Call#

1. Ensure the integration slug is exactly bitbucket.
2. Use clawlink_describe_tool to verify parameter names and types before calling.
3. For write operations, always call clawlink_preview_tool first.

Resources#

• Bitbucket Cloud REST API
• Bitbucket Repository API
• Bitbucket Pull Request API
• ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=bitbucket-repos
• ClawLink Docs: https://docs.claw-link.dev/openclaw
• ClawLink Verification: https://claw-link.dev/verify

Related Skills#

• GitHub — For GitHub repository operations
• GitLab — For GitLab repository operations
• Jira — For Jira issue tracking

---

Powered by ClawLink — an integration hub for OpenClaw