// Check gate status for a Bitbucket PR by resolving the PR head commit, finding the gate merge commit, inspecting builds on that merge commit, and summarizing root-cause failures with actionable next steps.
Create or update GraalPy third-party package compatibility patches under graalpython/lib-graalpython/patches, including PyPI source preparation, rebasing existing patches, metadata.toml updates, license checks, version-range validation, and verify_patches.py validation.
Analyze recent GraalPy benchmark regressions on `master` as part of the weekly rota. Use when asked to analyze benchmarks for rota.
Analyze current GraalPy periodic job failures for ROTA. Use when asked to triage, summarize, or plan work for current periodic job failures, starting from scripts/rota_ci_failures.py output, validating linked Jira issues, inspecting logs, forming hypotheses, reproduction commands, and implementation order.
Mirror an external GitHub pull request into the internal GraalPython Bitbucket review flow, including OCA label checks, Jira creation or reuse, preserving PR commits, pre-commit cleanup, and handoff to the shared GraalPython Bitbucket PR flow for PR creation, Graal Bot tasks, gates, and fixes.
Create or continue a GraalPython Bitbucket pull request and drive it through Graal Bot tasks, gate start, gate monitoring, failure investigation, fixes, pushes, and gate reruns. Use after a branch is ready for internal GraalPython review, or when an automation command has already created the PR and the remaining work is task cleanup and gate follow-up.
Run the GraalPy ROTA import update workflow. Use when asked to refresh imports, create the standard Graal import update pull request, inspect generated commits, and hand off to the shared GraalPython Bitbucket PR flow for tasks, gates, and failure fixes.
| name | pr-gate-check |
| description | Check gate status for a Bitbucket PR by resolving the PR head commit, finding the gate merge commit, inspecting builds on that merge commit, and summarizing root-cause failures with actionable next steps. |
Use this workflow when asked for gate status of a PR. Usually the builds are tied to a merge commit generated on Bitbucket, so this skill goes through finding the remote merge commit.
gdev-cli bitbucket commits output):gdev-cli bitbucket commits --project=G --repo=graalpython --pullrequest=<PR_ID> --all --json
git ls-remote origin 'refs/pull-requests/<PR_ID>/*'
git fetch --no-tags origin '+refs/heads/*:refs/remotes/origin/*' --prune
git rev-list --all --parents | rg ' <PR_HEAD_SHA>( |$)'
Pick the merge commit where one parent is <PR_HEAD_SHA> and the other is the target branch tip at merge time.
If you cannot find it this way, another heuristic is to take the branch name and append _gate - that usually has the merge commit we want as tip.
gdev-cli bitbucket get-builds --commit=<MERGE_SHA> --all --format=key,state,url
FAILED + /builders/.../builds/... URL: executed failed build (root failure candidate).FAILED + build_request?brid= URL: usually not-run/downstream due to earlier failure.Run executor stdio log.PR head: <sha>Gate merge commit: <sha> (parent1=<target_sha>, parent2=<pr_sha>)Builds: <total> total, <success> successful, <failed> failedRoot failure(s):<build key>: <error summary><failing test/path><build url>Proposed fixes: short list