bktlisted

# 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