[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EXCFW0V021HCPCP7FFMM5Y":3,"skill-same:01M7EXCFW0V021HCPCP7FFMM5Y":49},{"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":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7EXCFW0V021HCPCP7FFMM5Y","bitbucket-automation",null,"Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbitbucket-automation-antigravity-awesome-skills-main\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\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\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\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\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\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\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fbitbucket-automation-antigravity-awesome-skills-main",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill bitbucket-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill bitbucket-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill bitbucket-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fbitbucket-automation-antigravity-awesome-skills-main\u002FSKILL.md",true,[],[50,57,64,71,79,86],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7EXRM12046G0GM1WGMMFXCN","ci-cd-and-automation","Automates CI\u002FCD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fci-cd-and-automation\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7EXRFYYSJ3Y15AGPDDEWWQD","chrome-devtools","Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to `--slim` mode (MCP configuration).","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-devtools\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7EXR6EYPE4X5X1BTAE6QJRV","chrome-cdp","Drive a real Chrome via the Chrome DevTools Protocol (CDP). Ensures a\ndebuggable Chrome is running (launching it if needed) so the agent can\nnavigate, read page content, inspect the DOM, run JavaScript, and take\nscreenshots — without the user typing any launch command. Includes a\nfirst-class \"review a live running app\" flow: point Chrome at the app under\ndevelopment and inspect\u002Fscreenshot the REAL page (what a static-artifact tool\ncannot do). Backed by Glimpse and the chrome-devtools MCP server. Use when\nasked to \"use chrome\", \"open chrome\", \"drive my browser\", \"read the page in\nchrome\", \"review the running app\", \"screenshot the app\", or \"\u002Fchrome-cdp\".","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchrome-cdp\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":75,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7EXR1Y7E79KQKG4J798XGH6","check-identity-pack","Run an AFP 100-point or AUSTRAC safe-harbour identity check over a set of documents, and report exactly what's missing. Use when the user asks to check identity documents, verify someone's ID for onboarding, or assess whether a document pack satisfies Australian identity requirements.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcheck-identity-pack\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7EXQXW7C7PGREJW9ZZTZ16H","changelog","Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fchangelog\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7EXQMH2ZME3ANN8Q8MEWPFB","cellxgene-census","Query the CZ CELLxGENE Census programmatically for versioned public single-cell and spatial transcriptomics data. Use when you need population-scale cell metadata, gene expression slices, Census summary counts, source H5AD URIs\u002Fdownloads, embeddings, spatial Census data, or reference atlas comparisons across organisms, tissues, diseases, assays, and cell types. For analyzing your own local single-cell data use scanpy, anndata, or scvi-tools.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fcellxgene-census\u002FSKILL.md",[],[]]