Bitbucket Jira CLI

A gh-style CLI for Bitbucket pull requests, repos and pipelines, and Jira issues, with branch-name-as-Jira-key automation.

What it does¶

One-command install

A single uv command installs an isolated, self-updating CLI. No virtualenv juggling.

Installation
gh-style pull requests

Create, view, review and merge Bitbucket pull requests with the same noun-first ergonomics you know from gh.

Usage
Jira issues

Search (JQL), view, create, comment on and transition Jira issues without leaving the terminal.

Usage
Branch-key automation

Your branch name carries the Jira key. bj auto-links PRs to tickets and transitions them on create and merge.

Branch-key workflow
Pipelines

Trigger, list and stream logs for Bitbucket Pipelines, the gh run analog.

Pipeline reference
Ready for coding agents

Ships an Agent Skill so AI agents like Claude can drive bj the same way they drive gh.

Coding agents

Install, authenticate, ship. That is the whole flow.

Linux / macOSWindowsuvpipDocker

# Installs an isolated, self-updating CLI via uv.
curl -LsSf uvx.sh/bitbucket-jira-cli/install.sh | sh

powershell -ExecutionPolicy ByPass -c "irm https://uvx.sh/bitbucket-jira-cli/install.ps1 | iex"

# Install as an isolated tool...
uv tool install bitbucket-jira-cli

# ...or run it once without installing:
uvx bitbucket-jira-cli --help

pip install bitbucket-jira-cli

docker pull spenhouet/bitbucket-jira-cli:latest
docker run --rm spenhouet/bitbucket-jira-cli --help

bj auth login

# On a branch like feature/PROJ-42-thing, open a PR linked to PROJ-42:
bj pr create
bj pr view
bj issue view PROJ-42

Detailed setup lives in the installation docs.

Create a Jira issue, open a branch for it, and open a linked pull request, without leaving the terminal.