bitbucket-clilisted

# Bitbucket CLI Skill Bitbucket Cloud has no official first-party CLI equivalent to `gh`/`glab` — use the REST API via `curl` for all operations. ## Configuration Update the workspace below before using this skill: | Setting | Value | |---|---| | Bitbucket Workspace | `<your-workspace>` | | Credential File | `~/.bitbucket/token` | If the target workspace is unclear, ask the user before running any command. ### Prerequisites (one-time setup by user) Create an [App Password](https://bitbucket.org/account/settings/app-passwords/) with `Repositories: Read` (and `Write`/`Pull requests: Write` if mutations are needed), then save `<username>:<app-password>` to the credential file. Never print or display the credential value. Do not perform these steps yourself. ```bash mkdir -p ~/.bitbucket && echo "<username>:<app-password>" > ~/.bitbucket/token && chmod 600 ~/.bitbucket/token ``` ## Command Format All API calls use `curl` with basic auth read from the credential file: ```bash curl -s -u "$(cat ~/.bitbucket/token)" \ "https://api.bitbucket.org/2.0/<endpoint>" | jq . ``` ## PR Code Review When asked to review a Bitbucket PR (URL or PR ID provided), extract the `<workspace/repo>` and `<PR_ID>` from the URL (ask the user if the repo is missing), then fetch the PR metadata (`GET /2.0/repositories/<workspace>/<repo>/pullrequests/<PR_ID>`) and its diff (`GET /2.0/repositories/<workspace>/<repo>/pullrequests/<PR_ID>/diff`). To fully understand the context and impact of all