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

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

# bkt project

List and inspect Bitbucket projects. Projects are top-level containers that
group related repositories.

Note: Project commands are currently supported for Bitbucket Data Center only.
Cloud workspaces use a different organizational model and are managed through
other commands.

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

### Examples

```bash
# List all visible projects
  bkt project list

  # List projects on a specific host
  bkt project list --host my-dc-server
```

## Subcommands

| Subcommand | Description | Key Flags |
|---|---|---|
| [list](#bkt-project-list) | List Bitbucket Data Center projects *(DC)* | `--host`, `--limit` |
| [reviewer-groups](#bkt-project-reviewer-groups) | Work with project reviewer groups *(DC)* | — |

## bkt project list

List all projects visible to the authenticated user on a Bitbucket Data Center
instance. Each project is displayed with its key, name, description, web URL,
and visibility status. Use --limit to control the number of results returned.

This command is only available for Data Center hosts. Attempting to run it
against a Cloud context will return an error.

**Alias:** `ls`

### Usage

```
bkt project list [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--host` |  | Host key or base URL override |
| `--limit` |  | Maximum projects to display (0 for all) |

### 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 projects (default limit of 30)
  bkt project list

  # List all projects without a limit
  bkt project ls --limit 0

  # List projects on a specific Data Center host
  bkt project list --host my-dc-server

  # List projects in JSON format
  bkt project list --json
```

## bkt project reviewer-groups

List the reviewer groups defined in a project's settings.

Reviewer groups are named sets of users that can be added as default reviewers
on repositories within the project. Data Center only.

**Alias:** `reviewer-group`

```
bkt project reviewer-groups <command> [flags]
```

### Examples

```bash
# List reviewer groups for the active context project
  bkt project reviewer-groups list

  # List reviewer groups for a specific project
  bkt project reviewer-groups list --project PLATFORM
```

| Subcommand | Description |
|---|---|
| list | List project reviewer groups (DC only) |

## bkt project reviewer-groups list

List the reviewer groups defined in a Bitbucket Data Center project's
settings, including each group's members. The project is resolved from the
active context unless overridden with --project. Use --limit to control the
number of results returned.

This command is only available for Data Center hosts. Attempting to run it
against a Cloud context will return an error.

**Alias:** `ls`

### Usage

```
bkt project reviewer-groups list [flags]
```

### Flags

| Flag | Short | Description |
|---|---|---|
| `--limit` |  | Maximum reviewer groups to display (0 for all) |
| `--project` |  | Bitbucket project key 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 reviewer groups for the active context project (default limit of 30)
  bkt project reviewer-groups list

  # List all reviewer groups without a limit
  bkt project reviewer-groups ls --limit 0

  # List reviewer groups for a specific project
  bkt project reviewer-groups list --project PLATFORM

  # List reviewer groups in JSON format
  bkt project reviewer-groups list --project PLATFORM --json
```

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