菜单
Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/aAAaqwq/AGI-Super-Team --skill bitbucket-automation命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | bitbucket-automation |
| description | Automate Bitbucket repositories, pull requests, branches, issues, and workspace management via Rube MCP (Composio). Always search tools first for current schemas. |
| requires | {"mcp":["rube"]} |
Automate Bitbucket operations including repository management, pull request workflows, branch operations, issue tracking, and workspace administration through Composio's Bitbucket toolkit.
RUBE_MANAGE_CONNECTIONS with toolkit bitbucketRUBE_SEARCH_TOOLS first to get current tool schemasGet Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
RUBE_SEARCH_TOOLS respondsRUBE_MANAGE_CONNECTIONS with toolkit bitbucketWhen to use: User wants to create, review, or inspect pull requests
Tool sequence:
BITBUCKET_LIST_WORKSPACES - Discover accessible workspaces [Prerequisite]BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE - Find the target repository [Prerequisite]BITBUCKET_LIST_BRANCHES - Verify source and destination branches exist [Prerequisite]BITBUCKET_CREATE_PULL_REQUEST - Create a new PR with title, source branch, and optional reviewers [Required]BITBUCKET_LIST_PULL_REQUESTS - List PRs filtered by state (OPEN, MERGED, DECLINED) [Optional]BITBUCKET_GET_PULL_REQUEST - Get full details of a specific PR by ID [Optional]BITBUCKET_GET_PULL_REQUEST_DIFF - Fetch unified diff for code review [Optional]BITBUCKET_GET_PULL_REQUEST_DIFFSTAT - Get changed files with lines added/removed [Optional]Key parameters:
workspace: Workspace slug or UUID (required for all operations)repo_slug: URL-friendly repository namesource_branch: Branch with changes to mergedestination_branch: Target branch (defaults to repo main branch if omitted)reviewers: List of objects with uuid field for reviewer assignmentstate: Filter for LIST_PULL_REQUESTS - OPEN, MERGED, or DECLINEDmax_chars: Truncation limit for GET_PULL_REQUEST_DIFF to handle large diffsPitfalls:
reviewers expects an array of objects with uuid key, NOT usernames: [{"uuid": "{...}"}]{123e4567-e89b-12d3-a456-426614174000}destination_branch defaults to the repo's main branch if omitted, which may not be mainpull_request_id is an integer for GET/DIFF operations but comes back as part of PR listingmax_chars (e.g., 50000) on GET_PULL_REQUEST_DIFFWhen to use: User wants to list, create, or delete repositories or explore workspaces
Tool sequence:
BITBUCKET_LIST_WORKSPACES - List all accessible workspaces [Required]BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE - List repos with optional BBQL filtering [Required]BITBUCKET_CREATE_REPOSITORY - Create a new repo with language, privacy, and project settings [Optional]BITBUCKET_DELETE_REPOSITORY - Permanently delete a repository (irreversible) [Optional]BITBUCKET_LIST_WORKSPACE_MEMBERS - List members for reviewer assignment or access checks [Optional]Key parameters:
workspace: Workspace slug (find via LIST_WORKSPACES)repo_slug: URL-friendly name for create/deleteq: BBQL query filter (e.g., name~"api", project.key="PROJ", is_private=true)role: Filter repos by user role: member, contributor, admin, ownersort: Sort field with optional - prefix for descending (e.g., -updated_on)is_private: Boolean for repository visibility (defaults to true)project_key: Bitbucket project key; omit to use workspace's oldest projectPitfalls:
BITBUCKET_DELETE_REPOSITORY is irreversible and does not affect forksname~"my-repo" not name~my-reporepository is NOT a valid BBQL field; use name insteadpagelen explicitly for complete listingsCREATE_REPOSITORY defaults to private; set is_private: false for public reposWhen to use: User wants to create, update, list, or comment on repository issues
Tool sequence:
BITBUCKET_LIST_ISSUES - List issues with optional filters for state, priority, kind, assignee [Required]BITBUCKET_CREATE_ISSUE - Create a new issue with title, content, priority, and kind [Required]BITBUCKET_UPDATE_ISSUE - Modify issue attributes (state, priority, assignee, etc.) [Optional]BITBUCKET_CREATE_ISSUE_COMMENT - Add a markdown comment to an existing issue [Optional]BITBUCKET_DELETE_ISSUE - Permanently delete an issue [Optional]Key parameters:
issue_id: String identifier for the issuetitle, content: Required for creationkind: bug, enhancement, proposal, or taskpriority: trivial, minor, major, critical, or blockerstate: new, open, resolved, on hold, invalid, duplicate, wontfix, closedassignee: Bitbucket username for CREATE; assignee_account_id (UUID) for UPDATEdue_on: ISO 8601 format date stringPitfalls:
has_issues: true) or API calls will failCREATE_ISSUE uses assignee (username string), but UPDATE_ISSUE uses assignee_account_id (UUID) -- they are different fieldsDELETE_ISSUE is permanent with no undostate values include spaces: "on hold" not "on_hold"assignee in LIST_ISSUES uses account ID, not username; use "null" string for unassignedWhen to use: User wants to create branches or explore branch structure
Tool sequence:
BITBUCKET_LIST_BRANCHES - List branches with optional BBQL filter and sorting [Required]BITBUCKET_CREATE_BRANCH - Create a new branch from a specific commit hash [Required]Key parameters:
name: Branch name without refs/heads/ prefix (e.g., feature/new-login)target_hash: Full SHA1 commit hash to branch from (must exist in repo)q: BBQL filter (e.g., name~"feature/", name="main")sort: Sort by name or -target.date (descending commit date)pagelen: 1-100 results per page (default is 10)Pitfalls:
CREATE_BRANCH requires a full commit hash, NOT a branch name as target_hashrefs/heads/ prefix in branch names/, ., _, -)name~"feature/" not name~feature/When to use: User wants to add review comments to pull requests, including inline code comments
Tool sequence:
BITBUCKET_GET_PULL_REQUEST - Get PR details and verify it exists [Prerequisite]BITBUCKET_GET_PULL_REQUEST_DIFF - Review the actual code changes [Prerequisite]BITBUCKET_GET_PULL_REQUEST_DIFFSTAT - Get list of changed files [Optional]BITBUCKET_CREATE_PULL_REQUEST_COMMENT - Post review comments [Required]Key parameters:
pull_request_id: String ID of the PRcontent_raw: Markdown-formatted comment textcontent_markup: Defaults to markdown; also supports plaintextinline: Object with path, from, to for inline code commentsparent_comment_id: Integer ID for threaded replies to existing commentsPitfalls:
pull_request_id is a string in CREATE_PULL_REQUEST_COMMENT but an integer in GET_PULL_REQUESTinline.path at minimum; from/to are optional line numbersparent_comment_id creates a threaded reply; omit for top-level commentsAlways resolve human-readable names to IDs before operations:
BITBUCKET_LIST_WORKSPACES to get workspace slugsBITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE with q filter to find repo slugsBITBUCKET_LIST_BRANCHES to verify branch existence before PR creationBITBUCKET_LIST_WORKSPACE_MEMBERS to get UUIDs for reviewer assignmentBitbucket uses page-based pagination (not cursor-based):
page (starts at 1) and pagelen (items per page) parameterspagelen explicitly (max 50 for PRs, 100 for others)next URL or total count to determine if more pages existBitbucket Query Language is available on list endpoints:
name~"pattern"= (exact), ~ (contains), != (not equal), >, >=, <, <=AND / OR: name~"api" AND is_private=truemy-workspace) or UUID in braces ({uuid}){123e4567-e89b-12d3-a456-426614174000}assignee vs assignee_account_id: CREATE_ISSUE uses username, UPDATE_ISSUE uses UUIDstate values for issues include spaces: "on hold", not "on_hold"destination_branch omission defaults to repo main branch, not main literallyrepository is not a valid field -- use nameBITBUCKET_DELETE_REPOSITORY is irreversible and does not remove forksBITBUCKET_DELETE_ISSUE is permanent with no recovery option| Task | Tool Slug | Key Params |
|---|---|---|
| List workspaces | BITBUCKET_LIST_WORKSPACES | q, sort |
| List repos | BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE | workspace, q, role |
| Create repo | BITBUCKET_CREATE_REPOSITORY | workspace, repo_slug, is_private |
| Delete repo | BITBUCKET_DELETE_REPOSITORY | workspace, repo_slug |
| List branches | BITBUCKET_LIST_BRANCHES | workspace, repo_slug, q |
| Create branch | BITBUCKET_CREATE_BRANCH | workspace, repo_slug, name, target_hash |
| List PRs | BITBUCKET_LIST_PULL_REQUESTS | workspace, repo_slug, state |
| Create PR | BITBUCKET_CREATE_PULL_REQUEST | workspace, repo_slug, title, source_branch |
| Get PR details | BITBUCKET_GET_PULL_REQUEST | workspace, repo_slug, pull_request_id |
| Get PR diff | BITBUCKET_GET_PULL_REQUEST_DIFF | workspace, repo_slug, pull_request_id, max_chars |
| Get PR diffstat | BITBUCKET_GET_PULL_REQUEST_DIFFSTAT | workspace, repo_slug, pull_request_id |
| Comment on PR | BITBUCKET_CREATE_PULL_REQUEST_COMMENT | workspace, repo_slug, pull_request_id, content_raw |
| List issues | BITBUCKET_LIST_ISSUES | workspace, repo_slug, state, priority |
| Create issue | BITBUCKET_CREATE_ISSUE | workspace, repo_slug, title, content |
| Update issue | BITBUCKET_UPDATE_ISSUE | workspace, repo_slug, issue_id |
| Comment on issue | BITBUCKET_CREATE_ISSUE_COMMENT | workspace, repo_slug, issue_id, content |
| Delete issue | BITBUCKET_DELETE_ISSUE | workspace, repo_slug, issue_id |
| List members | BITBUCKET_LIST_WORKSPACE_MEMBERS | workspace |