vnordvnord/skills/bkt/SKILL.md

bkt

Skill1 starsChanged 4 months agoMITView on GitHub

Bitbucket CLI for Data Center and Cloud. Use when users need to manage repositories, pull requests, branches, issues, webhooks, or pipelines in Bitbucket. Triggers include "bitbucket", "bkt", "pull request", "PR", "repo list", "branch create", "Bitbucket Data Center", "Bitbucket Cloud", "keyring timeout".

Installs packages

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

avivsinai/bitbucket-clitheir own version, first seen Oct 25, 2026
mitchdowd/skillsedited, first seen Mar 30, 2026

Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
mitchdowd/skills★ 118% same
Wrote their own version · 1
avivsinai/bitbucket-cli★ 257same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- branch-review-canvasSkill
- grug-reviewSkill
- pairSkill
- terraformSkill
- walkthroughSkill

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Before any bkt command, verify install:
line 14
Very specific:
Do not proceed until bkt --version succeeds.
line 27
Very specific:
Use --json / --yaml on any command.
line 58
Distinctive:
When feedback targets specific code, post inline on file + line.
line 66

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Bitbucket CLI (bkt)

bkt is a unified CLI for Bitbucket Data Center and Bitbucket Cloud. It mirrors gh ergonomics and provides structured JSON/YAML output for automation.

Command syntax and flags: references/commands.md. Run bkt <command> --help when the reference is not enough.

Dependency check

Before any bkt command, verify install:

bkt --version

Platform	Command
macOS/Linux	`brew install avivsinai/tap/bitbucket-cli`
Windows	`scoop bucket add avivsinai https://github.com/avivsinai/scoop-bucket && scoop install bitbucket-cli`
Go	`go install github.com/avivsinai/bitbucket-cli/cmd/bkt@latest`
Binary	Download from GitHub Releases

Do not proceed until bkt --version succeeds.

Authentication

bkt auth login https://bitbucket.example.com --web          # DC
bkt auth login https://bitbucket.example.com --username alice --token <PAT>
bkt auth login https://bitbucket.org --kind cloud --web     # Cloud
bkt auth status

Bitbucket Cloud tokens: "API token with scopes", application Bitbucket, scope Account: Read (read:user:bitbucket); add Repositories / Pull requests / Issues as needed.

Contexts

bkt context create dc-prod --host bitbucket.example.com --project ABC --set-active
bkt context create cloud-team --host bitbucket.org --workspace myteam --set-active
bkt context list
bkt context use cloud-team

JSON output traps

List commands return wrapped objects, not bare arrays — --jq ".[]" fails.

Command	Root key
`bkt pr list --json`	`.pull_requests[]`
`bkt pr comments --json`	`.comments[]`

Use --json / --yaml on any command. Global overrides: --context, --project, --workspace, --repo.

Env: BKT_CONFIG_DIR, BKT_ALLOW_INSECURE_STORE, BKT_KEYRING_TIMEOUT (e.g. 2m).

Unwrapped endpoints: bkt api <path> --param ... --json.

PR comments: inline by default

When feedback targets specific code, post inline on file + line. Reserve general/activity comments for PR-wide remarks. One finding → one inline comment.

Flag	Purpose
`--text <msg>`	Comment body (required)
`--file <path>`	Repo-relative path in the diff; requires `--from-line` and/or `--to-line`
`--to-line <n>`	Line on the new side (most common)
`--from-line <n>`	Line on the old side (deletions)
`--parent <id>`	Reply in thread
`--pending`	Draft review comment

bkt pr comment 42 --file src/auth.ts --to-line 88 --text "..."
bkt pr comment 42 --parent 1001 --text "Fixed in the latest push."
bkt pr comment 42 --text "Overall LGTM; blocking on inline threads."

Parallel bkt pr comment calls are safe. Line numbers must sit on the diff hunk (read the current file for --to-line on Cloud).

Find open PR for current branch

No --source filter. Unwrap .pull_requests[]:

bkt pr list --state OPEN --json \
  | jq --arg b "$(git branch --show-current)" \
    '.pull_requests[] | select(.source.branch.name == $b) | {id, title}'

Resolve comment threads (Cloud)

bkt api "/2.0/repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/comments/{comment_id}/resolve" --method POST

Reopen: same URL, --method DELETE. Only inline/diff threads resolve; general comments often 403 — reply with bkt pr comment <id> --text "..." --parent <comment_id>.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free