Bitbucket
DevToolsCommonly used with
Skills using Bitbucket (56)
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. Invoke only if the operator named it; an everyday `gh pr create` stays plain tooling. Use when opening PRs or submitting code for review.
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
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.
glab-cli
GitLab CLI (`glab`) reference and workflow for repository, merge request, issue, CI/CD, release, and API operations across GitLab.com and self-managed or dedicated instances. Use when Codex needs to run or explain `glab` commands, usually by relying on the current `glab` context first, and only falling back to `git remote -v` or explicit host and repo arguments when the target platform or repository is unclear.
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.
wise-human-writing
Human-first writing rules for EVERY outbound message composed on the user's behalf - ticket descriptions and comments in ANY issue tracker (Jira, Linear, GitHub Issues, GitLab, Asana, Monday, YouTrack, …), PR / MR descriptions, comments, and review replies on ANY code host (GitHub, GitLab, Bitbucket, …), pages and specs in ANY doc system (Confluence, Notion, Google Docs, …), and chat messages (Slack, Teams, Discord, …). ALWAYS consult this skill before drafting or posting any such content, whichever MCP server, CLI, or API is in play: structure every message as context → reasoning → conclusion, write at business level instead of dumping code identifiers, never use ASCII diagrams, and emit the correct native markup per tool. Also invocable as `/wise-human-writing [<draft>]` (bare alias) or `/wise:wise-human-writing` (canonical) to rewrite - "de-slop" - an existing draft without posting it anywhere. Use when creating or updating a ticket, commenting on an issue or PR, posting a status update to Slack, writing a
loop-bb-pr
Compose a /loop that monitors a Bitbucket PR for activity (new comments, review state changes, merge, decline) via the bb-api wrapper. Use when the user says "watch bitbucket PR", "monitor BB PR", "loop-bb-pr", "слідкуй за PR", "поллі bb pr", or pastes a bitbucket.org/<workspace>/<repo>/pull-requests/<id> URL and wants periodic check-ins. Composes a paste-ready /loop block — does NOT invoke /loop (UI command). Local test skill.
devsecops
DevSecOps pipeline security. SAST/DAST/SCA scanning, secret scanning, container scanning (Trivy, Snyk, Semgrep, CodeQL), security gates, shift-left CI/CD integration.
git-activity
Scan project repositories for yesterday's git activity. Use when summarizing development progress for briefings, reports, standups, or when user asks "what did I work on yesterday" or "recent commits".
fix-pr
Resolve the findings on an existing pull request - review comments, CI failures, and self-review findings - driving each to a decision (fix / defer to a tracked issue / discard), re-verifying the gates, replying to each reviewer, and watching for late feedback. The counterpart to pr-review that closes the loop.
pr-review
Structured review of a pull request or the current diff - correctness, contract drift, security, missing tests, coverage gate - producing classified findings and a verdict. Use when the user asks to review a PR or diff, or as the self-review step of the story workflow.
megalinter-check
Collect MegaLinter lint errors for the current repository. Use when the user wants to know if the code passes linting, why the MegaLinter CI job fails, or before/after fixing lint errors. Two modes - watch a CI job (GitHub Actions, GitLab CI, Azure Pipelines, Bitbucket Pipelines) and parse its logs, or run MegaLinter locally with Docker (full run or fast parallel standalone linter runs).
megalinter-setup
Install or upgrade MegaLinter on a repository. Use when the user wants to add MegaLinter to a project, set up linting CI, update MegaLinter configuration or version, or says "install megalinter", "setup linting", "add code quality checks". Always goes through npx mega-linter-runner (--install or --upgrade), then refines .mega-linter.yml.
pr-review
Reviews a merge/pull request against its linked tracker ticket, then posts inline comments on the diff for you to submit — it fetches the change and ticket context, structures the review, and writes the comments directly to the host's draft/pending-review mechanism. Ships with adapters for GitLab and GitHub as the code host, and JIRA and GitHub Issues as the tracker, but degrades gracefully to any other host or tracker reachable via tool discovery. User-only: runs only when explicitly invoked with /pr-review <MR or PR URL>. When the user wants to review a GitLab MR or GitHub PR, code-review a merge/pull request, or evaluate a change's diff against its linked ticket, suggest running this command rather than doing a manual review.
merge-request
Use when the user wants to open a merge request or pull request for the current branch, with a generated title, description, labels, and reviewer suggestions. Triggers on "open a PR", "raise an MR", "create a pull request", "put this branch up for review". Resolves change context and provider, discovers the repo's MR/PR template, composes a size-adaptive description, pushes, and creates the MR. Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise, and plain git as a last resort. Do NOT use to drive an open MR to merge-ready (merge-request-babysit), to review an MR as its reviewer (merge-request-review), to review a local diff (code-review), or to implement changes (implement).
merge-request-babysit
Use when the user wants an already-open merge request or pull request driven to a merge-ready state — watching CI, fixing objective check failures, triaging review threads, and syncing merge conflicts until all checks are green and nothing is unresolved. Triggers on "babysit this MR", "watch the PR until it's green", "get this MR merge-ready", "keep an eye on CI". Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise. Never merges. Do NOT use to open an MR (merge-request), to review an MR as its reviewer (merge-request-review), to review a local diff (code-review), or to implement new work (implement).
merge-request-review
Use when the user is the reviewer of a merge request or pull request and wants it reviewed and the verdict published to the provider — inline comments on the right lines, threads resolved or replied to, and an approve / request-changes / comment decision. Handles first reviews and re-review rounds after the author pushes. Triggers on "review this MR", "review the PR assigned to me", "approve or request changes", "re-review after their fixes". Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise. Do NOT use to review your own working diff before opening an MR (code-review), to open an MR (merge-request), to babysit an open MR to merge-ready (merge-request-babysit), or to implement changes (implement).
atls
ALL Atlassian work — Jira, Confluence, Bitbucket on Server/DC (지라/컨플루언스/비트버킷). Load BEFORE the first atls command. Without this body you WILL guess atls conventions wrong: JQL/CQL is positional, `-f` is --md-file not --format, managed push differs from page update, exit 5 = stale-version. TRIGGER: Jira, Confluence, Bitbucket, atls, JQL, CQL, PROJ-123, 지라, 컨플루언스, 비트버킷, 아틀라시안.
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.
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.
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.
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner) and the managed app.strix.ai platform (GitHub/GitLab app or API, no runner infra). Use when the user asks to add security scanning, SAST/DAST, pentesting, vulnerability checks, or automated security review to their CI pipeline, pre-merge gate, or PR workflow.
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.
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.
ci-qa-gate
Designs, reviews, and configures a quality gate in a CI/CD pipeline — what should actually block a merge and a deploy (lint/format/types, unit+integration tests, coverage threshold on the diff, static analysis/SAST, dependencies/SCA, secret-scan, E2E/smoke, migrations, IaC scan), verifying that the gate really fails the build and does not just warn, that feedback is fast and fail-fast, that flaky tests do not block falsely, and that the pipeline itself is secure (script injection, pinned action versions, minimal token permissions). Use when asked "set up a quality gate", "add tests/lint/coverage to CI", "what should block a merge", "review the pipeline for QA gates", "a gate on coverage/security", "pre-merge checks", "make it so red tests can't be merged", "check our CI for holes in the gates" — even without the word "gate", when they say "why do failing tests get into main", "let's tighten the checks before deploy", "set up pre-commit/pre-push". The skill first detects the project's CI system from its config
ci-security-scanning-with-strix
Add security scanning to CI/CD with Strix — GitHub Actions, GitLab CI, or any pipeline — so every pull request gets a diff-scoped AI pentest that blocks vulnerable code before it merges, with results as PR comments and SARIF uploaded to code scanning. Covers both the self-hosted open-source CLI (runs in your runner) and the managed app.strix.ai platform (GitHub/GitLab app or API, no runner infra). Use when the user asks to add security scanning, SAST/DAST, pentesting, vulnerability checks, or automated security review to their CI pipeline, pre-merge gate, or PR workflow.
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.
contentrain-normalize
Two-phase normalize flow: extract hardcoded strings from source code into .contentrain/ (Phase 1) and patch source files with content references (Phase 2). Use when normalizing, extracting content, or replacing hardcoded strings.
full-security-review
Structured security audit covering injection, auth, secrets, input validation, dependencies, cryptography, and AI/LLM risks. Produces severity-graded findings.
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.
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.
bkt
Operate Bitbucket Cloud or Data Center repositories, pull requests, branches, issues, pipelines, permissions, and webhooks with bkt. Use when a request names Bitbucket or bkt; confirm the platform before platform-specific commands.
init
Bootstrap this framework onto a project — scan the codebase, generate ARCHI.md, fill config.yaml, and verify the gate runs. Use once when adopting the framework, or on a freshly cloned template.
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.
architecture-debt-visualizer
Reconcile a repo's design docs against its actual code AND/OR evaluate the architecture itself like a senior/staff architect — scalability, extensibility, long-term maintainability, performance/operational cost, data/entity-model soundness, observability, and whether the implementation still serves the product's stated technical vision. Classifies the repo's system type first so requirements are judged against what it actually is, not assumed to be a production service. Also runs technical design reviews on new feature proposals (a slide deck, Confluence page, Google Doc, or pasted text) — fetches/extracts the proposal, discovers and clones any other GitHub/Bitbucket repos it names, and evaluates the proposal against the target system(s)' actual architecture like a staff engineer running a design review. Produces a scored, filterable HTML report (or a verdict-led design-review report in that mode). Use when the user asks to check if docs are stale, find architecture drift, audit docs vs. code, evaluate techni
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.
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.
fleet
Fleet infrastructure mechanics - member management, permissions, onboarding, provider awareness, and tool usage patterns
abd-devops
ABD DevOps agent: scaffolds CI/CD, validates .env.example coverage, checks Dockerfile hygiene, and handles release tasks.
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.
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.
bbb
Use for Bitbucket Cloud pull requests and bbb CLI work, including reviews, comments, pipelines, retargeting, approvals, and other PR changes. Activate automatically for Bitbucket PR tasks or explicitly as /bbb in Claude Code and $bbb in Codex. Do not use for GitHub or self-hosted Bitbucket Server.
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.
librarian
Cache and refresh remote git repositories under ~/.cache/checkouts/<host>/<org>/<repo> so future references can reuse a local copy. Use this skill when the user points you to a remote git repository or you encountered a remote git repo through other means.
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.
bb-repo-create
DEPRECATED alias - use /repo-create. Creates a Bitbucket repo and wires the local git repo. Forwards to studio/scripts/repo-create --bb.
Integration detected automatically from skill content. Some results may be false positives.