[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76ZJ152C0ZP2PT0Z38Z2V80":3,"skill-same:01M76ZJ152C0ZP2PT0Z38Z2V80":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M76ZJ152C0ZP2PT0Z38Z2V80","bitbucket-automation",null,"Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsohamganatra\u002Fbitbucket-automation\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: bitbucket-automation\ndescription: Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.\nrequires:\n  mcp: [rube]\n---\n\n# Bitbucket Automation via Rube MCP\n\nAutomate Bitbucket operations including repository management, pull request workflows, branch operations, issue tracking, and workspace administration through Composio's Bitbucket toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Bitbucket connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bitbucket`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bitbucket`\n3. If connection is not ACTIVE, follow the returned auth link to complete Bitbucket OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Pull Requests\n\n**When to use**: User wants to create, review, or inspect pull requests\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_WORKSPACES` - Discover accessible workspaces [Prerequisite]\n2. `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` - Find the target repository [Prerequisite]\n3. `BITBUCKET_LIST_BRANCHES` - Verify source and destination branches exist [Prerequisite]\n4. `BITBUCKET_CREATE_PULL_REQUEST` - Create a new PR with title, source branch, and optional reviewers [Required]\n5. `BITBUCKET_LIST_PULL_REQUESTS` - List PRs filtered by state (OPEN, MERGED, DECLINED) [Optional]\n6. `BITBUCKET_GET_PULL_REQUEST` - Get full details of a specific PR by ID [Optional]\n7. `BITBUCKET_GET_PULL_REQUEST_DIFF` - Fetch unified diff for code review [Optional]\n8. `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` - Get changed files with lines added\u002Fremoved [Optional]\n\n**Key parameters**:\n- `workspace`: Workspace slug or UUID (required for all operations)\n- `repo_slug`: URL-friendly repository name\n- `source_branch`: Branch with changes to merge\n- `destination_branch`: Target branch (defaults to repo main branch if omitted)\n- `reviewers`: List of objects with `uuid` field for reviewer assignment\n- `state`: Filter for LIST_PULL_REQUESTS - `OPEN`, `MERGED`, or `DECLINED`\n- `max_chars`: Truncation limit for GET_PULL_REQUEST_DIFF to handle large diffs\n\n**Pitfalls**:\n- `reviewers` expects an array of objects with `uuid` key, NOT usernames: `[{\"uuid\": \"{...}\"}]`\n- UUID format must include curly braces: `{123e4567-e89b-12d3-a456-426614174000}`\n- `destination_branch` defaults to the repo's main branch if omitted, which may not be `main`\n- `pull_request_id` is an integer for GET\u002FDIFF operations but comes back as part of PR listing\n- Large diffs can overwhelm context; always set `max_chars` (e.g., 50000) on GET_PULL_REQUEST_DIFF\n\n### 2. Manage Repositories and Workspaces\n\n**When to use**: User wants to list, create, or delete repositories or explore workspaces\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_WORKSPACES` - List all accessible workspaces [Required]\n2. `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` - List repos with optional BBQL filtering [Required]\n3. `BITBUCKET_CREATE_REPOSITORY` - Create a new repo with language, privacy, and project settings [Optional]\n4. `BITBUCKET_DELETE_REPOSITORY` - Permanently delete a repository (irreversible) [Optional]\n5. `BITBUCKET_LIST_WORKSPACE_MEMBERS` - List members for reviewer assignment or access checks [Optional]\n\n**Key parameters**:\n- `workspace`: Workspace slug (find via LIST_WORKSPACES)\n- `repo_slug`: URL-friendly name for create\u002Fdelete\n- `q`: BBQL query filter (e.g., `name~\"api\"`, `project.key=\"PROJ\"`, `is_private=true`)\n- `role`: Filter repos by user role: `member`, `contributor`, `admin`, `owner`\n- `sort`: Sort field with optional `-` prefix for descending (e.g., `-updated_on`)\n- `is_private`: Boolean for repository visibility (defaults to `true`)\n- `project_key`: Bitbucket project key; omit to use workspace's oldest project\n\n**Pitfalls**:\n- `BITBUCKET_DELETE_REPOSITORY` is **irreversible** and does not affect forks\n- BBQL string values MUST be enclosed in double quotes: `name~\"my-repo\"` not `name~my-repo`\n- `repository` is NOT a valid BBQL field; use `name` instead\n- Default pagination is 10 results; set `pagelen` explicitly for complete listings\n- `CREATE_REPOSITORY` defaults to private; set `is_private: false` for public repos\n\n### 3. Manage Issues\n\n**When to use**: User wants to create, update, list, or comment on repository issues\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_ISSUES` - List issues with optional filters for state, priority, kind, assignee [Required]\n2. `BITBUCKET_CREATE_ISSUE` - Create a new issue with title, content, priority, and kind [Required]\n3. `BITBUCKET_UPDATE_ISSUE` - Modify issue attributes (state, priority, assignee, etc.) [Optional]\n4. `BITBUCKET_CREATE_ISSUE_COMMENT` - Add a markdown comment to an existing issue [Optional]\n5. `BITBUCKET_DELETE_ISSUE` - Permanently delete an issue [Optional]\n\n**Key parameters**:\n- `issue_id`: String identifier for the issue\n- `title`, `content`: Required for creation\n- `kind`: `bug`, `enhancement`, `proposal`, or `task`\n- `priority`: `trivial`, `minor`, `major`, `critical`, or `blocker`\n- `state`: `new`, `open`, `resolved`, `on hold`, `invalid`, `duplicate`, `wontfix`, `closed`\n- `assignee`: Bitbucket username for CREATE; `assignee_account_id` (UUID) for UPDATE\n- `due_on`: ISO 8601 format date string\n\n**Pitfalls**:\n- Issue tracker must be enabled on the repository (`has_issues: true`) or API calls will fail\n- `CREATE_ISSUE` uses `assignee` (username string), but `UPDATE_ISSUE` uses `assignee_account_id` (UUID) -- they are different fields\n- `DELETE_ISSUE` is permanent with no undo\n- `state` values include spaces: `\"on hold\"` not `\"on_hold\"`\n- Filtering by `assignee` in LIST_ISSUES uses account ID, not username; use `\"null\"` string for unassigned\n\n### 4. Manage Branches\n\n**When to use**: User wants to create branches or explore branch structure\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_BRANCHES` - List branches with optional BBQL filter and sorting [Required]\n2. `BITBUCKET_CREATE_BRANCH` - Create a new branch from a specific commit hash [Required]\n\n**Key parameters**:\n- `name`: Branch name without `refs\u002Fheads\u002F` prefix (e.g., `feature\u002Fnew-login`)\n- `target_hash`: Full SHA1 commit hash to branch from (must exist in repo)\n- `q`: BBQL filter (e.g., `name~\"feature\u002F\"`, `name=\"main\"`)\n- `sort`: Sort by `name` or `-target.date` (descending commit date)\n- `pagelen`: 1-100 results per page (default is 10)\n\n**Pitfalls**:\n- `CREATE_BRANCH` requires a full commit hash, NOT a branch name as `target_hash`\n- Do NOT include `refs\u002Fheads\u002F` prefix in branch names\n- Branch names must follow Bitbucket naming conventions (alphanumeric, `\u002F`, `.`, `_`, `-`)\n- BBQL string values need double quotes: `name~\"feature\u002F\"` not `name~feature\u002F`\n\n### 5. Review Pull Requests with Comments\n\n**When to use**: User wants to add review comments to pull requests, including inline code comments\n\n**Tool sequence**:\n1. `BITBUCKET_GET_PULL_REQUEST` - Get PR details and verify it exists [Prerequisite]\n2. `BITBUCKET_GET_PULL_REQUEST_DIFF` - Review the actual code changes [Prerequisite]\n3. `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` - Get list of changed files [Optional]\n4. `BITBUCKET_CREATE_PULL_REQUEST_COMMENT` - Post review comments [Required]\n\n**Key parameters**:\n- `pull_request_id`: String ID of the PR\n- `content_raw`: Markdown-formatted comment text\n- `content_markup`: Defaults to `markdown`; also supports `plaintext`\n- `inline`: Object with `path`, `from`, `to` for inline code comments\n- `parent_comment_id`: Integer ID for threaded replies to existing comments\n\n**Pitfalls**:\n- `pull_request_id` is a string in CREATE_PULL_REQUEST_COMMENT but an integer in GET_PULL_REQUEST\n- Inline comments require `inline.path` at minimum; `from`\u002F`to` are optional line numbers\n- `parent_comment_id` creates a threaded reply; omit for top-level comments\n- Line numbers in inline comments reference the diff, not the source file\n\n## Common Patterns\n\n### ID Resolution\nAlways resolve human-readable names to IDs before operations:\n- **Workspace**: `BITBUCKET_LIST_WORKSPACES` to get workspace slugs\n- **Repository**: `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` with `q` filter to find repo slugs\n- **Branch**: `BITBUCKET_LIST_BRANCHES` to verify branch existence before PR creation\n- **Members**: `BITBUCKET_LIST_WORKSPACE_MEMBERS` to get UUIDs for reviewer assignment\n\n### Pagination\nBitbucket uses page-based pagination (not cursor-based):\n- Use `page` (starts at 1) and `pagelen` (items per page) parameters\n- Default page size is typically 10; set `pagelen` explicitly (max 50 for PRs, 100 for others)\n- Check response for `next` URL or total count to determine if more pages exist\n- Always iterate through all pages for complete results\n\n### BBQL Filtering\nBitbucket Query Language is available on list endpoints:\n- String values MUST use double quotes: `name~\"pattern\"`\n- Operators: `=` (exact), `~` (contains), `!=` (not equal), `>`, `>=`, `\u003C`, `\u003C=`\n- Combine with `AND` \u002F `OR`: `name~\"api\" AND is_private=true`\n\n## Known Pitfalls\n\n### ID Formats\n- Workspace: slug string (e.g., `my-workspace`) or UUID in braces (`{uuid}`)\n- Reviewer UUIDs must include curly braces: `{123e4567-e89b-12d3-a456-426614174000}`\n- Issue IDs are strings; PR IDs are integers in some tools, strings in others\n- Commit hashes must be full SHA1 (40 characters)\n\n### Parameter Quirks\n- `assignee` vs `assignee_account_id`: CREATE_ISSUE uses username, UPDATE_ISSUE uses UUID\n- `state` values for issues include spaces: `\"on hold\"`, not `\"on_hold\"`\n- `destination_branch` omission defaults to repo main branch, not `main` literally\n- BBQL `repository` is not a valid field -- use `name`\n\n### Rate Limits\n- Bitbucket Cloud API has rate limits; large batch operations should include delays\n- Paginated requests count against rate limits; minimize unnecessary page fetches\n\n### Destructive Operations\n- `BITBUCKET_DELETE_REPOSITORY` is irreversible and does not remove forks\n- `BITBUCKET_DELETE_ISSUE` is permanent with no recovery option\n- Always confirm with the user before executing delete operations\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List workspaces | `BITBUCKET_LIST_WORKSPACES` | `q`, `sort` |\n| List repos | `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` | `workspace`, `q`, `role` |\n| Create repo | `BITBUCKET_CREATE_REPOSITORY` | `workspace`, `repo_slug`, `is_private` |\n| Delete repo | `BITBUCKET_DELETE_REPOSITORY` | `workspace`, `repo_slug` |\n| List branches | `BITBUCKET_LIST_BRANCHES` | `workspace`, `repo_slug`, `q` |\n| Create branch | `BITBUCKET_CREATE_BRANCH` | `workspace`, `repo_slug`, `name`, `target_hash` |\n| List PRs | `BITBUCKET_LIST_PULL_REQUESTS` | `workspace`, `repo_slug`, `state` |\n| Create PR | `BITBUCKET_CREATE_PULL_REQUEST` | `workspace`, `repo_slug`, `title`, `source_branch` |\n| Get PR details | `BITBUCKET_GET_PULL_REQUEST` | `workspace`, `repo_slug`, `pull_request_id` |\n| Get PR diff | `BITBUCKET_GET_PULL_REQUEST_DIFF` | `workspace`, `repo_slug`, `pull_request_id`, `max_chars` |\n| Get PR diffstat | `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` | `workspace`, `repo_slug`, `pull_request_id` |\n| Comment on PR | `BITBUCKET_CREATE_PULL_REQUEST_COMMENT` | `workspace`, `repo_slug`, `pull_request_id`, `content_raw` |\n| List issues | `BITBUCKET_LIST_ISSUES` | `workspace`, `repo_slug`, `state`, `priority` |\n| Create issue | `BITBUCKET_CREATE_ISSUE` | `workspace`, `repo_slug`, `title`, `content` |\n| Update issue | `BITBUCKET_UPDATE_ISSUE` | `workspace`, `repo_slug`, `issue_id` |\n| Comment on issue | `BITBUCKET_CREATE_ISSUE_COMMENT` | `workspace`, `repo_slug`, `issue_id`, `content` |\n| Delete issue | `BITBUCKET_DELETE_ISSUE` | `workspace`, `repo_slug`, `issue_id` |\n| List members | `BITBUCKET_LIST_WORKSPACE_MEMBERS` | `workspace` |\n","# Bitbucket Automation via Rube MCP\n\nAutomate Bitbucket operations including repository management, pull request workflows, branch operations, issue tracking, and workspace administration through Composio's Bitbucket toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Bitbucket connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bitbucket`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `bitbucket`\n3. If connection is not ACTIVE, follow the returned auth link to complete Bitbucket OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Manage Pull Requests\n\n**When to use**: User wants to create, review, or inspect pull requests\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_WORKSPACES` - Discover accessible workspaces [Prerequisite]\n2. `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` - Find the target repository [Prerequisite]\n3. `BITBUCKET_LIST_BRANCHES` - Verify source and destination branches exist [Prerequisite]\n4. `BITBUCKET_CREATE_PULL_REQUEST` - Create a new PR with title, source branch, and optional reviewers [Required]\n5. `BITBUCKET_LIST_PULL_REQUESTS` - List PRs filtered by state (OPEN, MERGED, DECLINED) [Optional]\n6. `BITBUCKET_GET_PULL_REQUEST` - Get full details of a specific PR by ID [Optional]\n7. `BITBUCKET_GET_PULL_REQUEST_DIFF` - Fetch unified diff for code review [Optional]\n8. `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` - Get changed files with lines added\u002Fremoved [Optional]\n\n**Key parameters**:\n- `workspace`: Workspace slug or UUID (required for all operations)\n- `repo_slug`: URL-friendly repository name\n- `source_branch`: Branch with changes to merge\n- `destination_branch`: Target branch (defaults to repo main branch if omitted)\n- `reviewers`: List of objects with `uuid` field for reviewer assignment\n- `state`: Filter for LIST_PULL_REQUESTS - `OPEN`, `MERGED`, or `DECLINED`\n- `max_chars`: Truncation limit for GET_PULL_REQUEST_DIFF to handle large diffs\n\n**Pitfalls**:\n- `reviewers` expects an array of objects with `uuid` key, NOT usernames: `[{\"uuid\": \"{...}\"}]`\n- UUID format must include curly braces: `{123e4567-e89b-12d3-a456-426614174000}`\n- `destination_branch` defaults to the repo's main branch if omitted, which may not be `main`\n- `pull_request_id` is an integer for GET\u002FDIFF operations but comes back as part of PR listing\n- Large diffs can overwhelm context; always set `max_chars` (e.g., 50000) on GET_PULL_REQUEST_DIFF\n\n### 2. Manage Repositories and Workspaces\n\n**When to use**: User wants to list, create, or delete repositories or explore workspaces\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_WORKSPACES` - List all accessible workspaces [Required]\n2. `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` - List repos with optional BBQL filtering [Required]\n3. `BITBUCKET_CREATE_REPOSITORY` - Create a new repo with language, privacy, and project settings [Optional]\n4. `BITBUCKET_DELETE_REPOSITORY` - Permanently delete a repository (irreversible) [Optional]\n5. `BITBUCKET_LIST_WORKSPACE_MEMBERS` - List members for reviewer assignment or access checks [Optional]\n\n**Key parameters**:\n- `workspace`: Workspace slug (find via LIST_WORKSPACES)\n- `repo_slug`: URL-friendly name for create\u002Fdelete\n- `q`: BBQL query filter (e.g., `name~\"api\"`, `project.key=\"PROJ\"`, `is_private=true`)\n- `role`: Filter repos by user role: `member`, `contributor`, `admin`, `owner`\n- `sort`: Sort field with optional `-` prefix for descending (e.g., `-updated_on`)\n- `is_private`: Boolean for repository visibility (defaults to `true`)\n- `project_key`: Bitbucket project key; omit to use workspace's oldest project\n\n**Pitfalls**:\n- `BITBUCKET_DELETE_REPOSITORY` is **irreversible** and does not affect forks\n- BBQL string values MUST be enclosed in double quotes: `name~\"my-repo\"` not `name~my-repo`\n- `repository` is NOT a valid BBQL field; use `name` instead\n- Default pagination is 10 results; set `pagelen` explicitly for complete listings\n- `CREATE_REPOSITORY` defaults to private; set `is_private: false` for public repos\n\n### 3. Manage Issues\n\n**When to use**: User wants to create, update, list, or comment on repository issues\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_ISSUES` - List issues with optional filters for state, priority, kind, assignee [Required]\n2. `BITBUCKET_CREATE_ISSUE` - Create a new issue with title, content, priority, and kind [Required]\n3. `BITBUCKET_UPDATE_ISSUE` - Modify issue attributes (state, priority, assignee, etc.) [Optional]\n4. `BITBUCKET_CREATE_ISSUE_COMMENT` - Add a markdown comment to an existing issue [Optional]\n5. `BITBUCKET_DELETE_ISSUE` - Permanently delete an issue [Optional]\n\n**Key parameters**:\n- `issue_id`: String identifier for the issue\n- `title`, `content`: Required for creation\n- `kind`: `bug`, `enhancement`, `proposal`, or `task`\n- `priority`: `trivial`, `minor`, `major`, `critical`, or `blocker`\n- `state`: `new`, `open`, `resolved`, `on hold`, `invalid`, `duplicate`, `wontfix`, `closed`\n- `assignee`: Bitbucket username for CREATE; `assignee_account_id` (UUID) for UPDATE\n- `due_on`: ISO 8601 format date string\n\n**Pitfalls**:\n- Issue tracker must be enabled on the repository (`has_issues: true`) or API calls will fail\n- `CREATE_ISSUE` uses `assignee` (username string), but `UPDATE_ISSUE` uses `assignee_account_id` (UUID) -- they are different fields\n- `DELETE_ISSUE` is permanent with no undo\n- `state` values include spaces: `\"on hold\"` not `\"on_hold\"`\n- Filtering by `assignee` in LIST_ISSUES uses account ID, not username; use `\"null\"` string for unassigned\n\n### 4. Manage Branches\n\n**When to use**: User wants to create branches or explore branch structure\n\n**Tool sequence**:\n1. `BITBUCKET_LIST_BRANCHES` - List branches with optional BBQL filter and sorting [Required]\n2. `BITBUCKET_CREATE_BRANCH` - Create a new branch from a specific commit hash [Required]\n\n**Key parameters**:\n- `name`: Branch name without `refs\u002Fheads\u002F` prefix (e.g., `feature\u002Fnew-login`)\n- `target_hash`: Full SHA1 commit hash to branch from (must exist in repo)\n- `q`: BBQL filter (e.g., `name~\"feature\u002F\"`, `name=\"main\"`)\n- `sort`: Sort by `name` or `-target.date` (descending commit date)\n- `pagelen`: 1-100 results per page (default is 10)\n\n**Pitfalls**:\n- `CREATE_BRANCH` requires a full commit hash, NOT a branch name as `target_hash`\n- Do NOT include `refs\u002Fheads\u002F` prefix in branch names\n- Branch names must follow Bitbucket naming conventions (alphanumeric, `\u002F`, `.`, `_`, `-`)\n- BBQL string values need double quotes: `name~\"feature\u002F\"` not `name~feature\u002F`\n\n### 5. Review Pull Requests with Comments\n\n**When to use**: User wants to add review comments to pull requests, including inline code comments\n\n**Tool sequence**:\n1. `BITBUCKET_GET_PULL_REQUEST` - Get PR details and verify it exists [Prerequisite]\n2. `BITBUCKET_GET_PULL_REQUEST_DIFF` - Review the actual code changes [Prerequisite]\n3. `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` - Get list of changed files [Optional]\n4. `BITBUCKET_CREATE_PULL_REQUEST_COMMENT` - Post review comments [Required]\n\n**Key parameters**:\n- `pull_request_id`: String ID of the PR\n- `content_raw`: Markdown-formatted comment text\n- `content_markup`: Defaults to `markdown`; also supports `plaintext`\n- `inline`: Object with `path`, `from`, `to` for inline code comments\n- `parent_comment_id`: Integer ID for threaded replies to existing comments\n\n**Pitfalls**:\n- `pull_request_id` is a string in CREATE_PULL_REQUEST_COMMENT but an integer in GET_PULL_REQUEST\n- Inline comments require `inline.path` at minimum; `from`\u002F`to` are optional line numbers\n- `parent_comment_id` creates a threaded reply; omit for top-level comments\n- Line numbers in inline comments reference the diff, not the source file\n\n## Common Patterns\n\n### ID Resolution\nAlways resolve human-readable names to IDs before operations:\n- **Workspace**: `BITBUCKET_LIST_WORKSPACES` to get workspace slugs\n- **Repository**: `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` with `q` filter to find repo slugs\n- **Branch**: `BITBUCKET_LIST_BRANCHES` to verify branch existence before PR creation\n- **Members**: `BITBUCKET_LIST_WORKSPACE_MEMBERS` to get UUIDs for reviewer assignment\n\n### Pagination\nBitbucket uses page-based pagination (not cursor-based):\n- Use `page` (starts at 1) and `pagelen` (items per page) parameters\n- Default page size is typically 10; set `pagelen` explicitly (max 50 for PRs, 100 for others)\n- Check response for `next` URL or total count to determine if more pages exist\n- Always iterate through all pages for complete results\n\n### BBQL Filtering\nBitbucket Query Language is available on list endpoints:\n- String values MUST use double quotes: `name~\"pattern\"`\n- Operators: `=` (exact), `~` (contains), `!=` (not equal), `>`, `>=`, `\u003C`, `\u003C=`\n- Combine with `AND` \u002F `OR`: `name~\"api\" AND is_private=true`\n\n## Known Pitfalls\n\n### ID Formats\n- Workspace: slug string (e.g., `my-workspace`) or UUID in braces (`{uuid}`)\n- Reviewer UUIDs must include curly braces: `{123e4567-e89b-12d3-a456-426614174000}`\n- Issue IDs are strings; PR IDs are integers in some tools, strings in others\n- Commit hashes must be full SHA1 (40 characters)\n\n### Parameter Quirks\n- `assignee` vs `assignee_account_id`: CREATE_ISSUE uses username, UPDATE_ISSUE uses UUID\n- `state` values for issues include spaces: `\"on hold\"`, not `\"on_hold\"`\n- `destination_branch` omission defaults to repo main branch, not `main` literally\n- BBQL `repository` is not a valid field -- use `name`\n\n### Rate Limits\n- Bitbucket Cloud API has rate limits; large batch operations should include delays\n- Paginated requests count against rate limits; minimize unnecessary page fetches\n\n### Destructive Operations\n- `BITBUCKET_DELETE_REPOSITORY` is irreversible and does not remove forks\n- `BITBUCKET_DELETE_ISSUE` is permanent with no recovery option\n- Always confirm with the user before executing delete operations\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List workspaces | `BITBUCKET_LIST_WORKSPACES` | `q`, `sort` |\n| List repos | `BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE` | `workspace`, `q`, `role` |\n| Create repo | `BITBUCKET_CREATE_REPOSITORY` | `workspace`, `repo_slug`, `is_private` |\n| Delete repo | `BITBUCKET_DELETE_REPOSITORY` | `workspace`, `repo_slug` |\n| List branches | `BITBUCKET_LIST_BRANCHES` | `workspace`, `repo_slug`, `q` |\n| Create branch | `BITBUCKET_CREATE_BRANCH` | `workspace`, `repo_slug`, `name`, `target_hash` |\n| List PRs | `BITBUCKET_LIST_PULL_REQUESTS` | `workspace`, `repo_slug`, `state` |\n| Create PR | `BITBUCKET_CREATE_PULL_REQUEST` | `workspace`, `repo_slug`, `title`, `source_branch` |\n| Get PR details | `BITBUCKET_GET_PULL_REQUEST` | `workspace`, `repo_slug`, `pull_request_id` |\n| Get PR diff | `BITBUCKET_GET_PULL_REQUEST_DIFF` | `workspace`, `repo_slug`, `pull_request_id`, `max_chars` |\n| Get PR diffstat | `BITBUCKET_GET_PULL_REQUEST_DIFFSTAT` | `workspace`, `repo_slug`, `pull_request_id` |\n| Comment on PR | `BITBUCKET_CREATE_PULL_REQUEST_COMMENT` | `workspace`, `repo_slug`, `pull_request_id`, `content_raw` |\n| List issues | `BITBUCKET_LIST_ISSUES` | `workspace`, `repo_slug`, `state`, `priority` |\n| Create issue | `BITBUCKET_CREATE_ISSUE` | `workspace`, `repo_slug`, `title`, `content` |\n| Update issue | `BITBUCKET_UPDATE_ISSUE` | `workspace`, `repo_slug`, `issue_id` |\n| Comment on issue | `BITBUCKET_CREATE_ISSUE_COMMENT` | `workspace`, `repo_slug`, `issue_id`, `content` |\n| Delete issue | `BITBUCKET_DELETE_ISSUE` | `workspace`, `repo_slug`, `issue_id` |\n| List members | `BITBUCKET_LIST_WORKSPACE_MEMBERS` | `workspace` |\n",{"name":5,"requires":24,"description":7},{"mcp":25},[26],"rube","main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fsohamganatra\u002Fbitbucket-automation",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill bitbucket-automation",{"tool":42,"command":43},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill bitbucket-automation",{"tool":45,"command":46},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill bitbucket-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsohamganatra\u002Fbitbucket-automation\u002FSKILL.md",true,[],[51,59,66,73,80,87],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":58},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":58},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":58},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":58},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":58},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":58},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]