Agent skill · software engineering · aiskillstore
bitbucket-jira-cli
Manage Bitbucket pull requests, repositories, and pipelines and Jira issues from the terminal with the bj CLI. bj mirrors the GitHub gh CLI, so gh pr/issue/repo commands map to bj pr/issue/repo, no MCP server or API wiring needed. Installs the bj CLI automatically if it is missing. Use when working with Bitbucket or Jira, opening or reviewing pull requests, managing Jira issues, running pipelines, or when a git branch name contains a Jira issue key like PROJ-42.
Why this skill is useful
Adds executable scripts for managing Bitbucket and Jira from the terminal, which are not commonly found in public documentation.
What it needs
Requires bitbucket-jira-cli installed locally. Requires bitbucket, jira account access. About 4k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
bitbucket-jira-cli (bj) bj is gh for Bitbucket and Jira. The command surface mirrors the GitHub CLI: if you know gh, you know bj. It manages Bitbucket pull requests, repositories, and pipelines, plus Jira issues, from one noun-first command tree. If a command or flag is not covered here, run bj <command> --help; the flags mirror gh and the help is authoritative. Install bj if it is missing Before running any bj command, make sure the CLI is on PATH. If command -v bj finds nothing, install it. This snippet picks whatever installer is already available and prefers an isolated, self-updating install: On Windows PowerShell, install with: Then verify, and fix PATH if the install dir is not picked up yet: To run bj once without installing it (one-off commands, ephemeral CI), use uvx bitbucket-jira-cli <args> in place of bj <args>. For repeated use in a session, install it once with the snippet above so later bj calls just work. Setup Authenticate once, like gh auth login: For CI or headless agents (no interactive prompt), pass tokens instead: Running non-interactively (agents, scripts, CI) Set BJPROMPTDISABLED=1 so bj never waits on a prompt; pass required values as flags or the command fails fast with a clear error. Piped output (non-TTY) already skips prompts. Set NOCOLOR=1 to drop colors and the spinner (less noise in the transcript). Add --json for the full, raw API payload; shape it with --jq '<expr>' (requires the jq binary on PATH). Pass --yes/-y to accept confirmations (merge, close, stop). Exit codes: 0 success, 1 failure (includes "not logged in"), 2 usage error. Branch on these instead of parsing text. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/bitbucket-jira-cli