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

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

# bkt context

Manage named contexts that store connection defaults for different Bitbucket
hosts, projects, workspaces, and repositories. Each context bundles a host with
its associated scope so you can switch between environments without repeating
flags on every command.

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

### Examples

```bash
# Create a Data Center context and make it active
  bkt context create work --host bitbucket.mycompany.com --project TEAM --set-active

  # List all configured contexts
  bkt context list

  # Switch to a different context
  bkt context use personal
```

## Subcommands

| Subcommand | Description | Key Flags |
|---|---|---|
| [create](#bkt-context-create) | Create a new CLI context | `--host`, `--project`, `--repo`, `--set-active` |
| [delete](#bkt-context-delete) | Delete a context | — |
| [list](#bkt-context-list) | List available contexts | — |
| [use](#bkt-context-use) | Activate an existing context | — |

## bkt context create

Create a named context that stores connection defaults for a Bitbucket host.
A context binds a host to a project (Data Center) or workspace (Cloud) and an
optional default repository, so subsequent commands inherit these values
without requiring flags.

### Usage

```
bkt context create <name> [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--host` |  | Host key or base URL (required) |
| `--project` |  | Default Bitbucket project key (Data Center) |
| `--repo` |  | Default repository slug |
| `--set-active` |  | Set the new context as active |
| `--workspace` |  | Default Bitbucket workspace (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
# Create a Data Center context
  bkt context create work --host bitbucket.mycompany.com --project TEAM

  # Create a Cloud context with a default repository
  bkt context create oss --host api.bitbucket.org --workspace my-team --repo api-service

  # Create a context and immediately make it active
  bkt context create staging --host staging.bb.internal --project OPS --set-active
```

## bkt context delete

Remove a named context from the configuration. If the deleted context is
currently active, the active context is cleared and you will need to select
another one with "bkt context use".

**Alias:** `rm`

### Usage

```
bkt context delete <name> [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
# Delete a context by name
  bkt context delete old-server

  # Delete using the short alias
  bkt context rm staging
```

## bkt context list

List all configured contexts along with their host, project or workspace,
and default repository. The currently active context is marked with an
asterisk (*).

**Alias:** `ls`

### Usage

```
bkt context list [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
# List all contexts
  bkt context list

  # List contexts using the short alias
  bkt context ls

  # List contexts as JSON
  bkt context list --json
```

## bkt context use

Set the named context as the active context. All subsequent commands will
resolve their host, project/workspace, and repository defaults from this
context unless overridden with explicit flags.

### Usage

```
bkt context use <name> [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
# Switch to the "work" context
  bkt context use work

  # Switch to a personal Cloud context
  bkt context use personal
```

writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 321kUpdated 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