hashgraph-online/awesome-codex-plugins / plugins/avivsinai/bitbucket-cli/skills/bkt
bkt
VerifiedOperate 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.9 KB |
| rules/admin.md | markdown | 5.3 KB |
| rules/auth.md | markdown | 8.4 KB |
| rules/branch.md | markdown | 12.6 KB |
| rules/commit.md | markdown | 2.2 KB |
| rules/context.md | markdown | 5.0 KB |
| rules/extension.md | markdown | 5.3 KB |
| rules/guide.md | markdown | 5.8 KB |
| rules/headless.md | markdown | 3.7 KB |
| rules/mcp.md | markdown | 29.1 KB |
| rules/other.md | markdown | 1.2 KB |
| rules/perms.md | markdown | 10.6 KB |
| rules/pipeline.md | markdown | 7.7 KB |
| rules/pr.md | markdown | 47.9 KB |
| rules/project.md | markdown | 4.2 KB |
| rules/repo.md | markdown | 14.0 KB |
| rules/skill.md | markdown | 17.1 KB |
| rules/status.md | markdown | 5.9 KB |
| rules/variable.md | markdown | 7.6 KB |
| rules/webhook.md | markdown | 6.7 KB |
rules/webhook.md
View on GitHub<!-- auto-generated by cmd/docgen — do not edit -->
# bkt webhook
Create, list, delete, and test webhooks on Bitbucket repositories.
Webhooks notify external services when events occur in a repository (e.g. push,
pull-request creation). Both Data Center and Cloud are supported, though the
identifier format differs: Data Center uses numeric IDs while Cloud uses UUIDs.
The test subcommand is available for Data Center only.
```
bkt webhook <command> [flags]
```
### Examples
```bash
# List all webhooks on the current repository
bkt webhook list
# Create a webhook for push events
bkt webhook create --name ci-trigger --url https://ci.example.com/hook --event repo:refs_changed
# Delete a webhook by ID (Data Center) or UUID (Cloud)
bkt webhook delete 42
```
## Subcommands
| Subcommand | Description | Key Flags |
|---|---|---|
| [create](#bkt-webhook-create) | Create a new webhook | `--active`, `--event`, `--name`, `--project` |
| [delete](#bkt-webhook-delete) | Delete a webhook | `--project`, `--repo`, `--workspace` |
| [list](#bkt-webhook-list) | List configured webhooks | `--project`, `--repo`, `--workspace` |
| [test](#bkt-webhook-test) | Trigger a webhook test delivery | `--project`, `--repo` |
## bkt webhook create
Create a new webhook on a Bitbucket repository.
You must specify a name, a callback URL, and at least one event to subscribe to.
The webhook is created active by default; pass --active=false to create it in a
disabled state.
Event names differ between Data Center and Cloud. For Data Center, common events
include repo:refs_changed and pr:opened. For Cloud, events follow the pattern
repo:push, pullrequest:created, and similar.
### Usage
```
bkt webhook create [flags]
```
### Flags
| Flag | Short | Description |
|---|---|---|
| `--active` | | Whether the webhook starts active |
| `--event` | | Events to subscribe to (repeatable) |
| `--name` | | Webhook name (required) |
| `--project` | | Bitbucket project key override (Data Center) |
| `--repo` | | Repository slug override |
| `--url` | | Webhook callback URL (required) |
| `--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
# Create a webhook for push events (Data Center)
bkt webhook create --name ci-trigger --url https://ci.example.com/hook --event repo:refs_changed
# Create a webhook for multiple events (Cloud)
bkt webhook create --name slack-notify --url https://hooks.slack.com/abc --event repo:push --event pullrequest:created
# Create a webhook in a disabled state
bkt webhook create --name staging-hook --url https://staging.example.com/hook --event repo:push --active=false
```
## bkt webhook delete
Delete a webhook from a Bitbucket repository.
For Data Center, pass the numeric webhook ID (shown by "bkt webhook list").
For Cloud, pass the webhook UUID. The webhook is removed immediately and cannot
be recovered.
**Alias:** `rm`
### Usage
```
bkt webhook delete <id|uuid> [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
# Delete a webhook by numeric ID (Data Center)
bkt webhook delete 42
# Delete a webhook by UUID (Cloud)
bkt webhook delete {a1b2c3d4-e5f6-7890-abcd-ef1234567890}
# Delete a webhook from a specific repository
bkt webhook delete 7 --project MYPROJ --repo my-repo
```
## bkt webhook list
List all webhooks configured on a Bitbucket repository.
For Data Center, the output includes the numeric webhook ID, status, name, and
callback URL. For Cloud, the output includes the webhook UUID, status, and URL.
Use --project/--repo for Data Center or --workspace/--repo for Cloud to override
the values from the current context.
**Alias:** `ls`
### Usage
```
bkt webhook list [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
# List webhooks using the current context
bkt webhook list
# List webhooks for a specific Data Center repository
bkt webhook list --project MYPROJ --repo my-repo
# List webhooks for a specific Cloud repository
bkt webhook list --workspace myteam --repo my-repo
```
## bkt webhook test
Send a test payload to a webhook's callback URL to verify connectivity.
This command is supported for Data Center only. It triggers a diagnostic POST
request from the Bitbucket server to the webhook's configured URL and reports
whether the delivery succeeded.
### Usage
```
bkt webhook test <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
# Test a webhook by ID
bkt webhook test 42
# Test a webhook in a specific repository
bkt webhook test 7 --project MYPROJ --repo my-repo
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| 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: 197k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |