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/pipeline.md

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

# bkt pipeline

Interact with Bitbucket Cloud Pipelines. Commands fail with an error for Data Center contexts.

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

## Subcommands

| Subcommand | Description | Key Flags |
|---|---|---|
| [list](#bkt-pipeline-list) | List recent pipeline runs *(Cloud)* | `--limit`, `--repo`, `--workspace` |
| [logs](#bkt-pipeline-logs) | Fetch logs for a pipeline run *(Cloud)* | `--repo`, `--step`, `--workspace` |
| [run](#bkt-pipeline-run) | Trigger a new pipeline run *(Cloud)* | `--interval`, `--max-interval`, `--ref`, `--repo` |
| [view](#bkt-pipeline-view) | Show details for a pipeline run *(Cloud)* | `--interval`, `--max-interval`, `--repo`, `--timeout` |

## bkt pipeline list

List recent pipeline runs for a Bitbucket Cloud repository.

Displays build number, UUID, state, result, target branch, and creation time for
each pipeline. By default the most recent 20 runs are shown; use --limit to adjust.
This command is available for Bitbucket Cloud contexts only.

**Alias:** `ls`

### Usage

```
bkt pipeline list [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--limit` |  | Maximum pipelines to display |
| `--repo` |  | Repository slug override |
| `--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 the 20 most recent pipeline runs
  bkt pipeline list

  # List the last 5 pipeline runs
  bkt pipeline list --limit 5

  # List pipelines for a specific repository
  bkt pipeline list --workspace myteam --repo backend-api
```

## bkt pipeline logs

Fetch logs for a pipeline run on Bitbucket Cloud.

Prints the log output for a pipeline step. By default the last step is selected;
use --step to target a specific step UUID. The <id> argument accepts either a build
number (e.g., 10) or a pipeline UUID. This command is available for Bitbucket Cloud
contexts only.

### Usage

```
bkt pipeline logs <id> [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--repo` |  | Repository slug override |
| `--step` |  | Specific step UUID to fetch logs for |
| `--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
# Fetch logs for the latest step of pipeline #42
  bkt pipeline logs 42

  # Fetch logs for a specific step
  bkt pipeline logs 42 --step '{step-uuid-here}'

  # Fetch logs using a pipeline UUID
  bkt pipeline logs '{a1b2c3d4-e5f6-7890-abcd-ef1234567890}'

  # Fetch logs for a pipeline in a specific repository
  bkt pipeline logs 10 --workspace myteam --repo backend-api
```

## bkt pipeline run

Trigger a new pipeline run on Bitbucket Cloud for the current repository.

The pipeline runs against the specified branch. Set --selector-type to choose a
pipeline definition for that branch target. For selector types other than default,
also set --selector-pattern. Selector values are passed directly to Bitbucket. You
can pass custom pipeline variables using the --var flag, which accepts KEY=VALUE
pairs and can be repeated. This command is available for Bitbucket Cloud contexts
only.

Use --wait to poll the triggered pipeline until it completes, with exponential
backoff and jitter. Exit codes in --wait mode: 0 = pipeline succeeded,
1 = pipeline completed unsuccessfully, 8 = timed out while still running, 130 = interrupted.

### Usage

```
bkt pipeline run [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--interval` |  | Initial polling interval when using --wait |
| `--max-interval` |  | Maximum polling interval (backoff cap) |
| `--ref` |  | Branch to run the pipeline on |
| `--repo` |  | Repository slug override |
| `--selector-pattern` |  | Pipeline definition name or pattern; omit for default |
| `--selector-type` |  | Pipeline selector type (for example custom or pull-requests) |
| `--timeout` |  | Maximum time to wait for the pipeline (0 for no timeout) |
| `--var` |  | Pipeline variable in KEY=VALUE form (repeatable) |
| `--wait` |  | Wait for the triggered pipeline to complete |
| `--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
# Run the pipeline on the main branch
  bkt pipeline run

  # Run the pipeline on a specific branch
  bkt pipeline run --ref feature/my-branch

  # Run a named custom pipeline
  bkt pipeline run --ref master --selector-type custom --selector-pattern deploy-to-production

  # Run with custom pipeline variables
  bkt pipeline run --ref main --var ENV=staging --var DEBUG=true

  # Run against a specific repository
  bkt pipeline run --workspace myteam --repo backend-api --ref develop

  # Trigger and wait for the result
  bkt pipeline run --ref main --wait
```

## bkt pipeline view

Show details for a pipeline run on Bitbucket Cloud.

Displays the pipeline state, result, and a breakdown of each step with its UUID,
status, and name. The <id> argument accepts either a build number (e.g., 10) or a
pipeline UUID. This command is available for Bitbucket Cloud contexts only.

Use --wait to poll until the pipeline completes, with exponential backoff and
jitter. Exit codes in --wait mode: 0 = pipeline succeeded, 1 = pipeline
completed unsuccessfully, 8 = timed out while still running, 130 = interrupted.

### Usage

```
bkt pipeline view <id> [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--interval` |  | Initial polling interval when using --wait |
| `--max-interval` |  | Maximum polling interval (backoff cap) |
| `--repo` |  | Repository slug override |
| `--timeout` |  | Maximum time to wait for the pipeline (0 for no timeout) |
| `--wait` |  | Wait for the pipeline to complete |
| `--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
# View pipeline run by build number
  bkt pipeline view 42

  # View pipeline run by UUID
  bkt pipeline view '{a1b2c3d4-e5f6-7890-abcd-ef1234567890}'

  # View a pipeline in a specific repository
  bkt pipeline view 10 --workspace myteam --repo backend-api

  # Wait for a running pipeline to finish
  bkt pipeline view 42 --wait
```

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