bkt

Bitbucket CLI (bkt)

Use bkt for Bitbucket Cloud and Data Center operations. Prefer structured

--json, --yaml, --jq, or --template output for automation.

Start with the requested operation

Run bkt --version only when installation or compatibility is uncertain. Run

bkt auth status when the command needs authentication or the active platform

and context are unknown. Do not make setup a prerequisite for an already

configured read-only request.

Cloud and Data Center have different feature sets. Determine the platform from

the active context or ask when it cannot be inferred. Do not suggest a Cloud-only

command for Data Center, or the reverse.

Read [setup and common workflows](rules/guide.md) when installing, authenticating,

creating a context, or learning the main command patterns. For config-free CI or

containers, read [headless authentication](rules/headless.md).

Route to the command reference

Read only the reference for the requested command group:

• [pull requests](rules/pr.md), [repositories](rules/repo.md),

[branches](rules/branch.md), [commits](rules/commit.md), or

[statuses](rules/status.md)

• [Cloud issues](rules/issue.md), [pipelines](rules/pipeline.md), or

[variables](rules/variable.md)

• [Data Center administration](rules/admin.md),

[projects](rules/project.md), or [permissions](rules/perms.md)

• [authentication](rules/auth.md), [contexts](rules/context.md),

[webhooks](rules/webhook.md), [extensions](rules/extension.md),

[MCP](rules/mcp.md), [skills](rules/skill.md), or [raw API](rules/other.md)

Mutation and credential boundaries

• Listing, viewing, status, and checks are read-only. Create, edit, approve,

merge, delete, rerun, or permission changes modify Bitbucket; perform them

only when the user requested that change.

• Never place tokens, OAuth secrets, or passwords in commands that could enter

logs or committed files. Use the CLI's supported credential flow or environment

variables described in the auth references.

• Official release binaries embed the Cloud browser-OAuth consumer credentials.

Do not remove that behavior as generic hardening. Source and Nix builds may

require BKT_OAUTH_CLIENT_ID and BKT_OAUTH_CLIENT_SECRET.

• Before a merge or other consequential write, inspect the exact target,

repository, and current checks. Report the resulting URL or identifier.

References

<!-- auto-generated by cmd/docgen — do not edit below this line -->

• [admin](rules/admin.md) — Administrative operations for Bitbucket (DC)
• [auth](rules/auth.md) — Manage Bitbucket authentication credentials
• [branch](rules/branch.md) — Inspect and manage branches
• [commit](rules/commit.md) — Work with commits
• [context](rules/context.md) — Manage Bitbucket CLI contexts
• [extension](rules/extension.md) — Manage bkt CLI extensions
• [issue](rules/issue.md) — Work with Bitbucket Cloud issues (Cloud)
• [mcp](rules/mcp.md) — Model Context Protocol server for agents
• [perms](rules/perms.md) — Manage Bitbucket permissions (DC)
• [pipeline](rules/pipeline.md) — Run and inspect Bitbucket Cloud pipelines (Cloud)
• [pr](rules/pr.md) — Manage pull requests
• [project](rules/project.md) — Work with Bitbucket projects (DC)
• [repo](rules/repo.md) — Work with Bitbucket repositories
• [skill](rules/skill.md) — Install and manage agent skills
• [status](rules/status.md) — Inspect commit and pull request statuses
• [variable](rules/variable.md) — Manage pipeline variables (Cloud)
• [webhook](rules/webhook.md) — Manage Bitbucket webhooks
• [other](rules/other.md) — api

<!-- end auto-generated -->