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

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

# bkt status

Inspect build and CI statuses attached to commits and pull requests. Subcommands
cover Data Center commit statuses, pull request head-commit statuses, Cloud
pipeline runs, and API rate-limit telemetry.

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

### Examples

```bash
# Show build statuses for a commit (Data Center)
  bkt status commit abc1234

  # Show build statuses for a pull request (Data Center)
  bkt status pr 42

  # Show a Cloud pipeline run
  bkt status pipeline {pipeline-uuid}

  # Check API rate limits for the active context
  bkt status rate-limit
```

## Subcommands

| Subcommand | Description | Key Flags |
|---|---|---|
| [commit](#bkt-status-commit) | Show the build statuses for a commit *(DC)* | — |
| [pipeline](#bkt-status-pipeline) | Show Bitbucket Cloud pipeline status *(Cloud)* | `--repo`, `--workspace` |
| [pr](#bkt-status-pr) | Show the build statuses for a pull request head commit *(DC)* | `--project`, `--repo` |
| [rate-limit](#bkt-status-rate-limit) | Show API rate limit telemetry for the active context | — |

## bkt status commit

Display the CI/build statuses reported against a specific commit SHA. Each
status includes the state (SUCCESSFUL, FAILED, INPROGRESS), the build key,
name, optional description, and a link to the build.

Currently supports Data Center contexts only. The commit does not need to
belong to any particular branch or pull request.

### Usage

```
bkt status commit <sha> [flags]
```

### 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
# Show statuses for a commit
  bkt status commit abc1234def5678

  # Show statuses using a full 40-character SHA
  bkt status commit 6f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a

  # Output as JSON
  bkt status commit abc1234 --json
```

## bkt status pipeline

Display the status of a Bitbucket Cloud Pipelines run identified by its UUID.
The output includes the pipeline state, result, target ref, creation and
completion timestamps, and a breakdown of individual steps with their names
and statuses.

The workspace and repository are resolved from the active Cloud context or
can be overridden with --workspace and --repo. This command requires a Cloud
context and does not work with Data Center.

### Usage

```
bkt status pipeline <uuid> [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--repo` |  | Repository slug override |
| `--workspace` |  | Bitbucket 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
# Show pipeline status by UUID
  bkt status pipeline {c0ffee42-abcd-1234-ef56-789012345678}

  # Override workspace and repo
  bkt status pipeline {c0ffee42-abcd-1234-ef56-789012345678} --workspace myteam --repo backend

  # Output as JSON
  bkt status pipeline {c0ffee42-abcd-1234-ef56-789012345678} --json
```

## bkt status pr

Look up the head (latest) commit of a pull request and display all CI/build
statuses attached to it. The output includes the pull request title and the
resolved commit SHA alongside the status details.

The project and repository are resolved from the active context or can be
overridden with --project and --repo. Currently supports Data Center
contexts only.

### Usage

```
bkt status pr <id> [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--project` |  | Bitbucket project key override |
| `--repo` |  | Repository slug 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
# Show statuses for pull request #42
  bkt status pr 42

  # Specify project and repo explicitly
  bkt status pr 42 --project MYPROJ --repo my-service

  # Output as JSON
  bkt status pr 42 --json
```

## bkt status rate-limit

Query the Bitbucket API and display the current rate-limit counters for the
active context. The output includes the overall limit, remaining requests,
reset time, and the header source from which the values were read.

Works on both Data Center and Cloud contexts. A lightweight ping request is
sent to populate the rate-limit headers before reporting.

### Usage

```
bkt status rate-limit [flags]
```

### 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
# Show rate limits for the active context
  bkt status rate-limit

  # Show rate limits as JSON
  bkt status rate-limit --json

  # Check rate limits for a specific context
  bkt status rate-limit --context my-cloud-ctx
```

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