Fix Ready PRs

Check the active checkout's branch with git symbolic-ref --quiet --short HEAD before running this workflow. On gitbutler/workspace, skip this skill and use fix-prs, preserving any narrower user scope. Its GitButler branch handling and review-resolution workflow take precedence; do not check out PR branches or use the Git-write commands below in that workspace.

Work through every open, non-draft pull request. Fix CI failures and unresolved Bugbot findings on the existing PR branch. Do not open a new PR for an existing one.

Drafts are out of scope unless the user names them.

1. Inventory

gh pr list --state open --limit 200 \
  --json number,title,isDraft,headRefName,headRepositoryOwner,isCrossRepository,url,mergeStateStatus

Keep only isDraft == false. Record number, branch, URL, and whether the head is a fork (isCrossRepository).

2. Collect failures

For each ready PR, gather current-head CI and unresolved Bugbot threads. Do not treat an in-progress check as green.

CI

gh pr checks <n>
gh pr view <n> --json statusCheckRollup,headRefOid

Treat as a failure when a required or repo workflow check is FAILURE, TIMED_OUT, ACTION_REQUIRED, or CANCELLED on the current head and has not been superseded by a newer run.

Ignore:

• SKIPPED / NEUTRAL
• Netlify header/pages/redirect checks and canceled deploy previews
• Mintlify Deployment skips
• macOS/Windows/iOS jobs that this repo skips on pull requests

If a failing job has logs, pull them:

gh run view <run-id> --log-failed

If checks are still IN_PROGRESS / pending, wait until they finish or fail before declaring the PR clean. Re-poll rather than guessing.

Bugbot

Use review threads, not only the Bugbot check conclusion. A green Bugbot check can still leave unresolved comments, and an older finding may already be fixed.