Menu

Individual skill

aai-bitbucket

0upvotes

Use aai-cli to inspect and manage Bitbucket repositories, pull requests, branches, commits, source files, comments, and pipelines.

api/domains/agents/aai_cli_skills/bundled/skills/aai-bitbucket/SKILL.md

Read pinned source

Source commit 724a8ace26035d19f64cc707fbc0b4ba110cbc95

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
111
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# aai-cli Bitbucket

Use this skill when working with Bitbucket Cloud through `aai-cli bitbucket`.

Before running commands, confirm the active profile or pass `--profile`. Repository-scoped commands accept `--repo`; newer repository commands also accept `--owner` plus `--repo`. `repos list` is workspace-scoped and accepts only `--limit` — never pass `--owner` to it. A `workspace/repo` value overrides the configured workspace.

For pull request review work, start with `prs get`, inspect changed files with `prs diffstat`, fetch large diffs with `prs diff --output`, and read exact file contents with `source get <commit> <path>` before commenting.

Successful output is JSON on stdout. Errors are structured JSON on stderr. See [the command reference](references/command-reference.md) for command shapes, response notes, and review workflows.