bitbucket-devopslisted

# Bitbucket DevOps Skill This skill provides comprehensive Bitbucket DevOps automation using direct Node.js API calls via the Bash tool. Built on the [bitbucket-mcp](https://github.com/Apra-Labs/bitbucket-mcp) client library. **Key Advantage:** Uses direct Node.js calls (auto-approved) instead of MCP tools, eliminating the approval prompts issue from [GitHub Issue #10801](https://github.com/anthropics/claude-code/issues/10801). ## ⚠️ MANDATORY: How to Approach User Requests **You MUST follow this three-tier fallback strategy for ALL Bitbucket operations. This is REQUIRED, not optional.** **CRITICAL RULES:** - **DO NOT create new .js files for Bitbucket API calls** - **DO NOT use `node -e` for inline Bitbucket API operations** - **ONLY use the pre-built CLI tools listed below** - **ALWAYS start with Tier 1, fall back to Tier 2 if needed, use Tier 3 only as last resort** ### Tier 1: High-Level Helper Functions (REQUIRED FIRST STEP) **You MUST check these helpers FIRST before attempting any other approach.** These solve common workflows in a single command. If the user's request matches any of these patterns, you MUST use the corresponding helper. **Location:** `~/.claude/skills/bitbucket-devops/lib/helpers.js` **Available Commands:** - `get-latest-failed <workspace> <repo>` - Get most recent failed pipeline - `get-latest <workspace> <repo>` - Get most recent pipeline (any status) - `get-by-number <workspace> <repo> <build-number>` - Find pipeline by build number - `ge