bitbucket-helper

Original：🇺🇸 English

Translated

1 scripts

Bitbucket PR operations: create, read, update, approve, diff.

10installs

Sourcedarknesskiller/skills

Added on2026-10-03

NPX Install

npx skill4agent add darknesskiller/skills bitbucket-helper

SKILL.md Content

View Translation Comparison →

Bitbucket Helper

Auto-detects Bitbucket Cloud or Server from configured git remote.

The helper script lives at

scripts/bitbucket_server_pr.py

relative to this skill's directory (the harness resolves it). Run it from the user's repo with the script's absolute or skill-relative path:

bash

python3 <skill-dir>/scripts/bitbucket_server_pr.py

Steps

Run helper with no args to detect type and PR context. Done when source, target, project, repo known.
PR body needed: use
```
/pr-writing
```
first. Done when body has Description, Test Plan, Test Result, Links.
Before live create/update/approve: confirm unless user explicitly asked.
For review: start with
```
review-context
```
, then targeted
```
diff --path
```
or
```
file
```
.
For updates: read PR version first, send only mutable fields (title, description, version, fromRef, toRef, reviewers). Never send
```
author
```
.

Completion: operation scoped to detected repo and PR, mutations authorized.

Commands

bash

# Read
list --repo-dir . [--state OPEN] [--limit 25] [--page-start 0]
get <pr_id> --repo-dir . [--body]
review-context <pr_id> --repo-dir .
files <pr_id> --repo-dir .
diff <pr_id> --repo-dir . --path <path>
file <path> --repo-dir . --at refs/heads/main
commits <pr_id> --repo-dir .
commit <sha> --repo-dir .

# Mutate
approve <pr_id> --repo-dir .
create --repo-dir . --target main --title "PROJ-123: title" [--draft]
update <pr_id> --repo-dir . [--refresh-description | --ready]

Flags:

--full

,

--body

,

--format text

,

--cloud

,

--base-url

.

Auth

BB_USER

/

BB_PASSWORD

or scoped:

BB_CLOUD_*

/

BB_SERVER_*

(scoped win). Cloud: App Password with Repositories and Pull Requests Read/Write.

SSH clone remotes are supported for repo detection. SSH keys authenticate Git transport only; REST API calls still need Bitbucket user/token credentials.

Detection

Remote	Type
`bitbucket.org` in URL	Cloud
`host/scm/` or `host/projects/`	Server

Override:

--cloud

or

--base-url

.