القائمة
Bitbucket code repository integration for managing repos, branches, PRs, issues, and CI/CD pipelines
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/Arvo-AI/aurora --skill bitbucketيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Datadog monitoring integration for querying logs, metrics, monitors, events, traces, hosts, and incidents during RCA investigations
GitHub code repository integration for investigating code changes, deployments, commits, PRs, and suggesting fixes during RCA
CloudBees CI integration for investigating builds, deployments, pipeline stages, and test results during RCA
عرض SKILL.md
| name | bitbucket |
| id | bitbucket |
| description | Bitbucket code repository integration for managing repos, branches, PRs, issues, and CI/CD pipelines |
| category | code_repository |
| connection_check | {"method":"get_credentials_from_db","provider_key":"bitbucket","required_field":"access_token"} |
| tools | ["bitbucket_repos","bitbucket_branches","bitbucket_pull_requests","bitbucket_issues","bitbucket_pipelines","bitbucket_fix"] |
| index | Code repo -- manage Bitbucket repos, branches, PRs, issues, CI/CD pipelines, and suggest code fixes (6 tools, 44 actions) |
| rca_priority | 2 |
| allowed-tools | bitbucket_repos, bitbucket_branches, bitbucket_pull_requests, bitbucket_issues, bitbucket_pipelines, bitbucket_fix |
| metadata | {"author":"aurora","version":"1.1"} |
Bitbucket code repository integration for managing repositories, branches, pull requests, issues, and CI/CD pipelines.
Connected account: {display_name}
Use bitbucket_repos(action='list_repos', workspace='WS') or bitbucket_repos(action='list_workspaces') to discover connected repos.
Workspace and repository auto-resolve from saved user selection if not passed explicitly.
bitbucket_repos -- Repository, File & Code Operations:
list_repos, get_repo, get_file_contents, find_in_file, edit_file, create_or_update_file, delete_fileget_directory_tree, search_code, list_workspaces, get_workspacebitbucket_branches -- Branch & Commit Operations:
list_branches, create_branch, delete_branch, list_commits, get_commit, get_diff, comparebitbucket_pull_requests -- Pull Request Operations:
list_prs, get_pr, create_pr, update_pr, merge_pr, approve_pr, unapprove_pr, decline_prlist_pr_comments, add_pr_comment, get_pr_diff, get_pr_activitybitbucket_issues -- Issue Operations:
list_issues, get_issue, create_issue, update_issue, list_issue_comments, add_issue_commentbitbucket_pipelines -- CI/CD Pipeline Operations:
list_pipelines, get_pipeline, trigger_pipeline, stop_pipelinelist_pipeline_steps, get_step_log, get_pipeline_stepedit_file (anchored search-and-replace applied server-side against the true current file) for ANY change to an existing file. Use create_or_update_file ONLY for brand-new paths — never to overwrite a file you already read via a full-content upload.get_file_contents and copy old_string byte-for-byte from the output. Keep old_string narrow — the changed lines plus 1-3 lines of surrounding context. Do NOT pass the whole file as old_string.[lines X-Y of N — pass start_line=<n> commit=<sha> to continue] (or start_char=<offset> for one oversized line) — follow it verbatim to read further; the commit=<sha> pin keeps every page on the same file version even if the branch moves. Every page is exact file content, never a summary.find_in_file (locate the lines to change, returns L<line>: <text> matches plus the resolved commit) → get_file_contents with start_line=<match line> and that commit (read that region verbatim) → edit_file with narrow anchors. You do not need the whole file in context to edit it. find_in_file matches your query as a literal substring first, then as a regex.edit_file call can carry several edits (scattered locations = one commit); multiple files = multiple edit_file calls on the same branch = one PR.edit_file on that branch, then open a PR. During background RCA: repo tools are read-only — use bitbucket_fix to propose changes instead.bitbucket_fix -- Suggest Code Fixes During RCA:
file_path, edits (list of {old_string, new_string, replace_all}), fix_description, root_cause_summaryrepo (workspace/repo_slug), commit_message, branchbitbucket_repos(action='list_repos', workspace='WS')bitbucket_branches(action='list_commits', workspace='WS', repo_slug='REPO')bitbucket_pull_requests(action='list_prs', workspace='WS', repo_slug='REPO', state='MERGED')bitbucket_pipelines(action='list_pipelines', workspace='WS', repo_slug='REPO')bitbucket_pipelines(action='get_step_log', workspace='WS', repo_slug='REPO', pipeline_uuid='UUID', step_uuid='UUID')bitbucket_branches(action='get_diff', workspace='WS', repo_slug='REPO', spec='COMMIT_SHA')bitbucket_fix(file_path='path/to/file', edits=[{old_string: '...', new_string: '...'}], fix_description='...', root_cause_summary='...')list_repos and list_workspaces return only the repos/workspaces the user has connected — not everything in their Bitbucket account.repo_slug auto-resolve from saved selection if not passed explicitly.bitbucket_fix to propose code changes — it saves suggestions for user review.bitbucket_fix does NOT modify the repo directly — it saves the suggestion for user review. No confirmation needed.bitbucket_fix to propose a revert or correction.bitbucket_fix instead; the user will create the PR from the Incidents UI after reviewing your suggestion. During Aurora Actions / interactive chat, the branch → edit_file → PR workflow described above IS the correct way to ship a change.