bkt

原文涵盖的主题

• Bitbucket CLI (bkt)
• Start with the requested operation
• Route to the command reference
• Mutation and credential boundaries
• References

Use bkt for Bitbucket Cloud and Data Center operations. Prefer structured --json, --yaml, --jq, or --template output for automation. 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 when installing, authenticating, creating a context, or learning the main command patterns. For config-free CI or containers, read headless authentication. Read only the reference for the requested command group: pull requests, repositories, branches, commits, or statuses pipelines or variables Bitbucket Cloud Issues no longer exist (Atlassian removed them in August 2026); route issue tracking to Jira. Data Center administration, projects, or permissions authentication, contexts, webhooks, extensions, MCP, skills, or raw API Listing, viewing, status, and checks are read-

这里只展示节选，请以完整原文和当前要求为准。