skills/bitbucket/SKILL.md
Bitbucket integration hub. Detects whether the repository is on Bitbucket Cloud or Bitbucket Data Center and directs you to the matching detailed skill (bitbucket-cloud or bitbucket-data-center). Use for any Bitbucket repository or pull request task.
npx skillsauth add openhands/extensions bitbucketInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are working with Bitbucket, which ships as two distinct products that behave differently:
bitbucket.org) — authenticates with the BITBUCKET_TOKEN
environment variable.BITBUCKET_DATA_CENTER_TOKEN environment variable.They use different REST APIs, repository identifiers, git remote URL formats, and pull request tools, so you must first determine which one you are on, then load the matching detailed skill for full instructions.
Check which token environment variable is present. Environment variable names are case-sensitive, so look for it case-insensitively:
env | grep -i 'bitbucket' || echo "no bitbucket token found"
BITBUCKET_DATA_CENTER_TOKEN variable is set (in any letter case) → you are on
Bitbucket Data Center.BITBUCKET_TOKEN variable is set → you are on Bitbucket Cloud.When you reference the token later, use the exact variable name (and letter case) that actually exists in the environment.
Once you know the environment, use the invoke_skill tool to load the matching skill for
full instructions on API calls, authenticated git remotes, and opening pull requests:
bitbucket-cloud skill.bitbucket-data-center skill.If you are unable to load the detailed skill, these are the essentials. Always use the Bitbucket API (not a web browser) and always use the listed PR tool to open a pull request.
| | Bitbucket Cloud | Bitbucket Data Center |
|---|---|---|
| Token env var | BITBUCKET_TOKEN | BITBUCKET_DATA_CENTER_TOKEN |
| Host | bitbucket.org | self-hosted domain |
| REST API base | https://api.bitbucket.org/2.0 | https://<host>/rest/api/1.0 |
| Repository identifier | workspace/repo_slug | PROJECT/repo_slug (project key) |
| Pull request tool | create_bitbucket_pr | create_bitbucket_data_center_pr |
tools
Iterate on a GitHub pull request — drive it through CI, code review, and QA until it is merge-ready. Poll verification layers with `gh` CLI, diagnose and fix CI failures, address review feedback, retry flaky checks, push fixes, and repeat. The agent is the orchestration loop.
development
Guides technical explanations toward flowing, direct, conversational prose. This skill should be used for engineering chat, design discussion, architecture analysis, code-review explanations, and technical recommendations that should be concise without becoming fragmented or vague.
tools
This skill should be used when the user asks to "set up a Jira automation to create pull requests", "poll Jira for create-pr issues", "automatically create GitHub PRs from Jira tickets", "deploy a Jira issue-to-PR automation", "create a Jira to GitHub PR workflow", or mentions automating GitHub PR creation from a Jira label. Deploys a cron-based OpenHands automation that watches a Jira Cloud project for issues labeled with a configurable label (default: "create-pr") and spawns an agent conversation to create a GitHub pull request for each new issue found. The target GitHub repository is read from the body of the Jira ticket - no repo parameter is required at deploy time.
tools
This skill should be used when the user asks to "create an automation", "schedule a task", "set up a cron job", "webhook integration", "event-triggered automation", or mentions automations, scheduled tasks, cron scheduling, or webhook events in OpenHands Cloud.