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/commit.md
View on GitHub<!-- auto-generated by cmd/docgen — do not edit -->
# bkt commit
Inspect and compare commits in a Bitbucket repository. Subcommands let you
view diffs between two commits or refs. Works with both Bitbucket Cloud and
Data Center; on Cloud the diff spec uses ".." notation, while on Data Center
the two refs are passed separately to the API.
```
bkt commit <command> [flags]
```
### Examples
```bash
# Show changes between two commit SHAs
bkt commit diff abc1234 def5678
# Compare a branch to main
bkt commit diff feature/login main
```
## Subcommands
| Subcommand | Description | Key Flags |
|---|---|---|
| [diff](#bkt-commit-diff) | Show the diff between two commits or refs | `--project`, `--repo`, `--workspace` |
## bkt commit diff
Display a unified diff between two commits, branches, or tags. The output is
streamed through the configured pager when available.
On Data Center the two refs are resolved independently by the server. On Cloud
the refs are joined with ".." and sent as a single diff spec; note that branch
names containing literal ".." characters may confuse the Cloud API.
Use --project/--repo (DC) or --workspace/--repo (Cloud) to override the values
from the current context.
### Usage
```
bkt commit diff <from> <to> [flags]
```
### Flags
| Flag | Short | Description |
|---|---|---|
| `--project` | | Bitbucket project key override |
| `--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
# Diff two commits
bkt commit diff abc1234 def5678
# Diff the current branch against main
bkt commit diff feature/signup main
# Diff with explicit repo override
bkt commit diff v1.0.0 v1.1.0 --repo my-service
# Diff on a Cloud workspace
bkt commit diff develop main --workspace myteam --repo backend
```
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: 196k | 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 |