Bitbucket
DevToolsCommonly used with
Skills using Bitbucket (29)
release
Generic release assistant — analyzes repo release rules, caches them in .omc/RELEASE_RULE.md, then guides the release
bitbucket-automation
Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.
qodo-pr-resolver
Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)
ci
Detect/generate/debug CI pipeline config (GitHub Actions, GitLab CI). Triggers: CI setup, build pipeline, GitHub Actions config, debug CI, GitLab CI.
atlassian-admin
Atlassian Administrator for managing and organizing Atlassian products (Jira, Confluence, Bitbucket, Trello), users, permissions, security, integrations, system configuration, and org-wide governance. Use when asked to add users to Jira, change Confluence permissions, configure access control, update admin settings, manage Atlassian groups, set up SSO, install marketplace apps, review security policies, or handle any org-wide Atlassian administration task.
bkt
Bitbucket CLI for Data Center and Cloud. Use when users need to manage repositories, pull requests, branches, issues, webhooks, or pipelines in Bitbucket. Triggers include "bitbucket", "bkt", "pull request", "PR", "repo list", "branch create", "Bitbucket Data Center", "Bitbucket Cloud", "keyring timeout".
create-pr
Creates GitHub pull requests with pre-flight validation, conventional title formatting, and structured summary generation. Runs parallel checks (tests, lint, type-check, security) before opening. Supports feature, bugfix, refactor, and hotfix PR types with milestone assignment via gh CLI. Use when opening PRs or submitting code for review.
repo-explorer
Explore and analyze any repository (local path or remote GitHub/GitLab URL) by delegating to Claude Code CLI (`claude -p`) in non-interactive mode with read-only access. Use when the user asks to explore, analyze, investigate, or research a repository or codebase. Triggers on "explore repo", "analyze repo", "investigate repo", "research codebase", "what does this repo do", "how does this codebase work", "ask about repo", "codebase question", "explore repository", "what API does this project have", "analyze this GitHub repo", "explore https://github.com/...", or any request to understand a repository's structure, API, architecture, or implementation details. Works with both local paths and remote URLs (GitHub, GitLab, Bitbucket).
migrate-to-teamcity
Migrating CI/CD pipelines to TeamCity. Use when the user wants to migrate, convert, or switch to TeamCity from GitHub Actions (.github/workflows/) or Bamboo (bamboo-specs/*.yml), even if they only say "move our CI". Other CI systems (GitLab, Jenkins, CircleCI, Azure DevOps, Travis, Bitbucket) are not supported yet.
ci
CI/CD pipeline integration. Use when setting up or checking CI quality gates, exporting rules to GitHub Actions/GitLab CI/Bitbucket/Jenkins, or verifying pipeline alignment with local rules.
dev-pr
Operator-sanctioned alternative to bare `git push` from agent context. Open a PR from the current feature branch with a body assembled inline from commit history, the test command's last output, screenshots, and an optional project PR template. Refuses on protected branches, dirty trees, or zero commits ahead. Run as the final step of a ticket.
extract-api
This skill should be used when the user asks to "extract API from", "import API from", "add commands from this repo", "register API from docs", "convert docs to CLI commands", "import Postman collection", or provides a GitHub repository URL, a documentation site URL, a Postman collection file/URL, or a local API documentation file and wants it imported as sdkck CLI commands.
sidekick
ALWAYS run `sdkck search` FIRST before using ANY tool, MCP server, Bash command, or external API. sdkck is the canonical command surface for Jira, Sentry, MySQL, Postgres, Supabase, Bitbucket, Confluence, and imported OpenAPI/Postman specs. Trigger on every task involving external systems, APIs, databases, tickets, errors, wikis, repos, or third-party services — search sidekick before reaching for MCP or shell equivalents.
pipeline-security
Security scanning templates and HARD-RULES for CI/CD pipeline configuration. Covers Semgrep SAST and TruffleHog secret scanning across Bitbucket, GitHub Actions, GitLab CI, and Azure DevOps.
weekly-report
Generates a git-based team development report — commits, merged PRs, contributor activity, statistics over a time window. Use when the user asks "weekly report", "what did we ship", "sprint summary", "team contributions", or "show merged PRs this week". Distinct from session-report (per-session), Jira reports, postmortems, code review reports, and non-git data sources.
git-ticket
Use when the user wants to open a GitHub issue or pull request, a GitLab issue or merge request, or any forge ticket from their case/context — "create a github issue", "open a PR", "raise a MR", "file a bug", "open a merge request", "make a pull request for this branch". Also use when they mention a house title convention like `[API/{MODULE}] summary`, or when a forge CLI is missing/unauthed and they need a title + markdown body to paste in manually. Covers GitHub (gh) and GitLab (glab); unknown hosts (Bitbucket, self-hosted) fall back to markdown. Also use for GitHub Projects v2 board actions — "close this ticket", "close issue #N", "move this to In Progress", "advance this card to Ready", "move #N to Done" — scoped to the project linked to the current repo. GitHub only for now.
pr-review
HEAVYWEIGHT, GitHub-only deep PR review. Takes a GitHub PR URL, prepares a read-only git worktree at the PR head (SSH clone only), and reviews the diff with full cross-file context via Read/Grep/Glob. Fans out one agent per dimension (correctness, security, tests, performance, api, docs, observability, concurrency, feature-flow) through the Workflow tool, then adversarially verifies every finding before it survives. Traces feature flags / experiments via the statsig MCP and pulls linked Jira/Confluence via the atlassian MCP. Posts inline review comments, a review summary, and appreciations through the gh CLI after confirmation. NEVER merges, never force-pushes, never edits the PR's code. For a quick read-only pass with no worktree, use /adk:review.
integration-specialist-agent
Resilient third-party integration patterns — API clients, webhooks, MCP server wiring, retries/circuit-breakers, and idempotency. Use when connecting to an external service (Stripe/GitHub/Slack/S3/etc.), building or verifying a webhook receiver, adding retry/backoff or circuit-breaker resilience, registering an MCP server, or reviewing an integration for signature-verification and rate-limit gaps.
ws-jira-conventions
WS Agency Jira commit/branch/PR conventions. Use when working with Jira tickets, writing commits that reference issue keys (e.g. WSC-123), naming branches, or composing PR titles. Documents the project's Conventional Commits + Jira suffix format and Smart Commit syntax.
bkt
Bitbucket CLI for Data Center and Cloud. Use when users need to manage repositories, pull requests, branches, issues, webhooks, or pipelines in Bitbucket. Triggers include "bitbucket", "bkt", "pull request", "PR", "repo list", "branch create", "Bitbucket Data Center", "Bitbucket Cloud", "keyring timeout".
pr-review-skill-generator
Generate a repo-specific PR-review skill by mining recently merged PRs — review comments, enforced corrections, accepted patterns, domain vocabulary, and post-merge fixes — into a distilled reviewer skill with provenance and a measured backtest score. Use when asked to generate, train, build, regenerate, or update a PR review skill from a repository's history.
ci
Generate a CI/CD pipeline — build, test, security scan, deploy. Supports GitHub Actions, GitLab CI, Bitbucket Pipelines.
sap-btp-devops
SAP BTP DevOps — CI/CD pipeline configuration, MTA build automation, automated testing, transport integration (CTMS), GitHub Actions for BTP, SAP Continuous Integration and Delivery service, Jenkins. Use when setting up CI/CD for BTP, configuring deployment pipelines, or connecting Git to BTP deployments.
codecov
Query Codecov for flaky-test signal, failure history, and coverage data via the codecov-api wrapper. Use when asked about flaky tests, intermittent test failures, why a test is failing, coverage on a PR/file/branch, or whenever browser access to Codecov is blocked by the login wall.
pull-request
Use BEFORE opening or drafting ANY pull request — when asked to "open a PR", "create a pull request", "draft a PR", or to write a PR title/description. Covers summarizing the whole branch, the Jira key as title prefix (never in the body), GitHub vs Bitbucket creation, and the rule that a PR carries NO AI attribution.
bb-bash
Use this skill when the user asks about a Bitbucket Cloud pull request — listing PRs, reading diffs, posting comments, leaving inline review feedback, approving, declining, merging, or creating new PRs. Triggers on phrases like "review the PR", "comment on PR
add-blocker
Attach a new blocker (GitHub issue, URL, local file, or freeform statement) to an already-started Ogre issue, and force the plan to be revised to account for it.
aitask-learn-skill
Learn a new skill from sources — a local file, a URL, a repo file/dir, or a tmux pane (capturing the workflow an agent just ran) — and generate a complete static SKILL.md.
aitask-contribute
Contribute changes back to repositories by opening structured issues (GitHub, GitLab, or Bitbucket). Supports both aitasks framework contributions and project-specific contributions.
Integration detected automatically from skill content. Some results may be false positives.