bitbucket

You are working with Bitbucket, which ships as two distinct products that behave
differently:

• Bitbucket Cloud (bitbucket.org) — authenticates with the BITBUCKET_TOKEN
  environment variable.
• Bitbucket Data Center (self-hosted Bitbucket Server) — authenticates with the
  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.

Step 1 — Detect which Bitbucket you are on

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"

• If a BITBUCKET_DATA_CENTER_TOKEN variable is set (in any letter case) → you are on
  Bitbucket Data Center.
• Otherwise, if a BITBUCKET_TOKEN variable is set → you are on Bitbucket Cloud.
• If neither is set, ask the user how they authenticate to Bitbucket before proceeding.

When you reference the token later, use the exact variable name (and letter case) that
actually exists in the environment.

Step 2 — Load the detailed skill

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 → invoke the bitbucket-cloud skill.
• Bitbucket Data Center → invoke the bitbucket-data-center skill.

Quick reference (fallback)

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.