Skip to content

hashgraph-online/awesome-codex-plugins / plugins/avivsinai/bitbucket-cli/skills/bkt

Operate Bitbucket Cloud or Data Center repositories, pull requests, branches, pipelines, permissions, and webhooks with bkt. Use when a request names Bitbucket or bkt; confirm the platform before platform-specific commands.

FileKindSize
SKILL.mdskill md3.9 KB
rules/admin.mdmarkdown5.3 KB
rules/auth.mdmarkdown8.4 KB
rules/branch.mdmarkdown12.6 KB
rules/commit.mdmarkdown2.2 KB
rules/context.mdmarkdown5.0 KB
rules/extension.mdmarkdown5.3 KB
rules/guide.mdmarkdown5.8 KB
rules/headless.mdmarkdown3.7 KB
rules/mcp.mdmarkdown29.1 KB
rules/other.mdmarkdown1.2 KB
rules/perms.mdmarkdown10.6 KB
rules/pipeline.mdmarkdown7.7 KB
rules/pr.mdmarkdown47.9 KB
rules/project.mdmarkdown4.2 KB
rules/repo.mdmarkdown14.0 KB
rules/skill.mdmarkdown17.1 KB
rules/status.mdmarkdown5.9 KB
rules/variable.mdmarkdown7.6 KB
rules/webhook.mdmarkdown6.7 KB

rules/repo.md

View on GitHub
<!-- auto-generated by cmd/docgen — do not edit -->

# bkt repo

Work with Bitbucket repositories on both Data Center and Cloud.

List, view, create, clone, and browse repositories within a project (Data Center)
or workspace (Cloud). Use --project for Data Center hosts and --workspace for
Cloud hosts when the active context does not define defaults.

```
bkt repo <command> [flags]
```

## Subcommands

| Subcommand | Description | Key Flags |
|---|---|---|
| [browse](#bkt-repo-browse) | Print the repository web URL | `--project`, `--repo`, `--workspace` |
| [clone](#bkt-repo-clone) | Clone a repository | `--dest`, `--project`, `--ssh`, `--workspace` |
| [create](#bkt-repo-create) | Create a new repository | `--cloud-project`, `--default-branch`, `--description`, `--forkable` |
| [default-reviewers](#bkt-repo-default-reviewers) | List effective default reviewers for a repository | — |
| [downloads](#bkt-repo-downloads) | Work with repository downloads *(Cloud)* | — |
| [list](#bkt-repo-list) | List repositories within the active scope | `--limit`, `--project`, `--workspace` |
| [view](#bkt-repo-view) | Display details for a repository | `--project`, `--repo`, `--workspace` |

## bkt repo browse

Print the repository web URL using the active context defaults.

Override the target repository with an argument or --repo flag. Set --project
for Bitbucket Data Center hosts or --workspace for Bitbucket Cloud hosts when
the context does not define defaults.

### Usage

```
bkt repo browse [<repository>] [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--project` |  | Bitbucket project key override (Data Center) |
| `--repo` |  | Repository slug override |
| `--workspace` |  | Bitbucket workspace override (Cloud) |

### Inherited Flags

| Flag | Short | Description |
|---|---|---|
| `--context` | `-c` | Active Bitbucket context name |
| `--format` |  | Output format: json or yaml (alias for --json/--yaml) |
| `--jq` |  | Apply a jq expression to JSON output (requires --json or --format json) |
| `--json` |  | Output in JSON format when supported |
| `--template` |  | Render output using Go templates |
| `--yaml` |  | Output in YAML format when supported |

### Examples

```bash
# open the active context default repository
  bkt repo browse

  # override the repository slug
  bkt repo browse platform-api

  # override both project and repo for Bitbucket Data Center
  bkt repo browse --project DATA --repo pipeline-api
```

## bkt repo clone

Clone a Bitbucket repository to your local machine.

Resolves the clone URL from the Bitbucket API using the active context. By
default the HTTPS clone URL is used; pass --ssh to use the SSH URL instead.
Use --dest to specify a destination directory.

Works with both Data Center (requires --project or context default) and Cloud
(requires --workspace or context default).

### Usage

```
bkt repo clone <repository> [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--dest` |  | Destination directory |
| `--project` |  | Bitbucket project key override |
| `--ssh` |  | Use SSH clone URL |
| `--workspace` |  | Bitbucket workspace override (Cloud) |

### Inherited Flags

| Flag | Short | Description |
|---|---|---|
| `--context` | `-c` | Active Bitbucket context name |
| `--format` |  | Output format: json or yaml (alias for --json/--yaml) |
| `--jq` |  | Apply a jq expression to JSON output (requires --json or --format json) |
| `--json` |  | Output in JSON format when supported |
| `--template` |  | Render output using Go templates |
| `--yaml` |  | Output in YAML format when supported |

### Examples

```bash
# Clone the specified repository
  bkt repo clone my-service

  # Clone using SSH
  bkt repo clone my-service --ssh

  # Clone into a specific directory
  bkt repo clone my-service --dest ~/projects/my-service

  # Clone from a specific Data Center project
  bkt repo clone my-service --project PLATFORM
```

## bkt repo create

Create a new repository in a Bitbucket project (Data Center) or workspace (Cloud).

On Data Center, the repository is created under the specified project with optional
flags for visibility, forking policy, SCM, and default branch. On Cloud, the
repository is created in the specified workspace; use --cloud-project to assign
it to a Bitbucket Cloud project. Repositories are private by default on Cloud;
pass --public to make them public.

Host-specific flags are validated before any API request. Data Center accepts
--project, --forkable, --default-branch, and --scm. Cloud accepts --workspace
and --cloud-project. Passing a flag that only applies to the other host kind
returns an error instead of silently ignoring it.

### Usage

```
bkt repo create <repository> [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--cloud-project` |  | Bitbucket Cloud project key |
| `--default-branch` |  | Data Center default branch to set after creation |
| `--description` |  | Repository description |
| `--forkable` |  | Allow forking of the Data Center repository |
| `--project` |  | Bitbucket Data Center project key override |
| `--public` |  | Create repository as public |
| `--scm` |  | Data Center SCM type (git) |
| `--workspace` |  | Bitbucket Cloud workspace override |

### Inherited Flags

| Flag | Short | Description |
|---|---|---|
| `--context` | `-c` | Active Bitbucket context name |
| `--format` |  | Output format: json or yaml (alias for --json/--yaml) |
| `--jq` |  | Apply a jq expression to JSON output (requires --json or --format json) |
| `--json` |  | Output in JSON format when supported |
| `--template` |  | Render output using Go templates |
| `--yaml` |  | Output in YAML format when supported |

### Examples

```bash
# Create a repository in the active context
  bkt repo create my-new-service

  # Create a public repository with a description
  bkt repo create my-lib --public --description "Shared utility library"

  # Create in a specific Data Center project with a default branch
  bkt repo create api-gateway --project PLATFORM --default-branch main

  # Create in a Cloud workspace and assign to a project
  bkt repo create frontend-app --workspace my-team --cloud-project WEB
```

## bkt repo default-reviewers

Manage default reviewers configured for a repository.

On Cloud, returns the effective default reviewers (merged from workspace and
repository-level settings). On Data Center, returns the effective default
reviewers for a pull request from --source to --target.

```
bkt repo default-reviewers <command> [flags]
```

| Subcommand | Description |
|---|---|
| list | List default reviewers |

## bkt repo default-reviewers list

List the default reviewers configured for a repository.

On Cloud, this returns the effective default reviewers that would be automatically
added to new pull requests, including reviewers inherited from workspace-level
settings. On Data Center, this returns the effective default reviewers that would
be added to a pull request from --source to --target. Data Center requires
source and target branch or tag names.

The workspace/project and repository are resolved from the active context unless
overridden with flags.

### Usage

```
bkt repo default-reviewers list [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--project` |  | Bitbucket project key override |
| `--repo` |  | Repository slug override |
| `--source` |  | Data Center source branch or tag |
| `--target` |  | Data Center target branch or tag |
| `--workspace` |  | Bitbucket Cloud workspace override |

### Inherited Flags

| Flag | Short | Description |
|---|---|---|
| `--context` | `-c` | Active Bitbucket context name |
| `--format` |  | Output format: json or yaml (alias for --json/--yaml) |
| `--jq` |  | Apply a jq expression to JSON output (requires --json or --format json) |
| `--json` |  | Output in JSON format when supported |
| `--template` |  | Render output using Go templates |
| `--yaml` |  | Output in YAML format when supported |

### Examples

```bash
# List default reviewers for the active context repository
  bkt repo default-reviewers list

  # List default reviewers for a specific Cloud repository
  bkt repo default-reviewers list --workspace my-team --repo api-service

  # List default reviewers for a Data Center repository
  bkt repo default-reviewers list --project PLATFORM --repo backend --source feature/auth --target main
```

## bkt repo downloads

Manage files in a Bitbucket Cloud repository's Downloads section.

Downloads is the only place the public API accepts arbitrary file uploads
for a repository, which makes it the way to host images for pull request
descriptions and comments. Workspaces on the Free plan cannot upload or
download files; the API rejects those requests.

**Alias:** `download`

```
bkt repo downloads <command> [flags]
```

| Subcommand | Description |
|---|---|
| list | List repository downloads (Cloud only) |
| upload | Upload files to the repository downloads (Cloud only) |

## bkt repo downloads list

List repository downloads (Cloud only)

### Usage

```
bkt repo downloads list [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--repo` |  | Repository slug |
| `--workspace` |  | Bitbucket workspace |

### Inherited Flags

| Flag | Short | Description |
|---|---|---|
| `--context` | `-c` | Active Bitbucket context name |
| `--format` |  | Output format: json or yaml (alias for --json/--yaml) |
| `--jq` |  | Apply a jq expression to JSON output (requires --json or --format json) |
| `--json` |  | Output in JSON format when supported |
| `--template` |  | Render output using Go templates |
| `--yaml` |  | Output in YAML format when supported |

### Examples

```bash
# List downloads of the active context repository
  bkt repo downloads list

  # List downloads of a specific repository as JSON
  bkt repo downloads list --workspace my-team --repo api-service --json
```

## bkt repo downloads upload

Upload one or more files to a Bitbucket Cloud repository's Downloads section
and print their URLs.

An existing download with the same file name is replaced, so give images
unique names. All files are validated before any upload begins. Directories
cannot be uploaded.

Downloads are visible to everyone with access to the repository. Do not
upload anything that should stay private to a subset of them.

### Usage

```
bkt repo downloads upload <files>... [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--repo` |  | Repository slug |
| `--workspace` |  | Bitbucket workspace |

### Inherited Flags

| Flag | Short | Description |
|---|---|---|
| `--context` | `-c` | Active Bitbucket context name |
| `--format` |  | Output format: json or yaml (alias for --json/--yaml) |
| `--jq` |  | Apply a jq expression to JSON output (requires --json or --format json) |
| `--json` |  | Output in JSON format when supported |
| `--template` |  | Render output using Go templates |
| `--yaml` |  | Output in YAML format when supported |

### Examples

```bash
# Upload a screenshot and print its URL
  bkt repo downloads upload screenshot.png

  # Upload several images and get Markdown image links for a PR description
  bkt repo downloads upload before.png after.png --json --jq '.downloads[] | "![" + .name + "](" + .url + ")"'
```

## bkt repo list

List repositories in a Bitbucket project (Data Center) or workspace (Cloud).

On Data Center, a project key is required via --project or the active context.
On Cloud, a workspace is required via --workspace or the active context.
Use --limit to control the number of results (0 returns all).

**Alias:** `ls`

### Usage

```
bkt repo list [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--limit` |  | Maximum repositories to display (0 for all) |
| `--project` |  | Bitbucket project key override |
| `--workspace` |  | Bitbucket workspace override (Cloud) |

### Inherited Flags

| Flag | Short | Description |
|---|---|---|
| `--context` | `-c` | Active Bitbucket context name |
| `--format` |  | Output format: json or yaml (alias for --json/--yaml) |
| `--jq` |  | Apply a jq expression to JSON output (requires --json or --format json) |
| `--json` |  | Output in JSON format when supported |
| `--template` |  | Render output using Go templates |
| `--yaml` |  | Output in YAML format when supported |

### Examples

```bash
# List repositories in the active context
  bkt repo list

  # List repositories in a specific Data Center project
  bkt repo list --project MYPROJ

  # List repositories in a Cloud workspace with a custom limit
  bkt repo list --workspace my-team --limit 50

  # List all repositories (no limit)
  bkt repo list --limit 0
```

## bkt repo view

Display details for a repository, including its name, web URL, and clone URLs.
On Data Center, output also includes whether the repository is archived.

On Data Center, the project key and repository slug are resolved from the active
context or overridden with --project and --repo. On Cloud, the workspace and
repository slug are resolved similarly via --workspace and --repo.

Pass a repository slug as an argument or use the --repo flag.

### Usage

```
bkt repo view [repository] [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--project` |  | Bitbucket project key override |
| `--repo` |  | Repository slug override |
| `--workspace` |  | Bitbucket workspace override (Cloud) |

### Inherited Flags

| Flag | Short | Description |
|---|---|---|
| `--context` | `-c` | Active Bitbucket context name |
| `--format` |  | Output format: json or yaml (alias for --json/--yaml) |
| `--jq` |  | Apply a jq expression to JSON output (requires --json or --format json) |
| `--json` |  | Output in JSON format when supported |
| `--template` |  | Render output using Go templates |
| `--yaml` |  | Output in YAML format when supported |

### Examples

```bash
# View the repository configured in the active context
  bkt repo view

  # View a specific repository by slug
  bkt repo view my-service

  # View a Data Center repository with explicit project
  bkt repo view --project PLATFORM --repo api-gateway

  # View a Cloud repository in a specific workspace
  bkt repo view --workspace my-team --repo frontend-app
```

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall