merge-github-prlisted

# Merge GitHub PR ## Purpose Merge pull requests that meet all required conditions. --- ## Constraints - Apply @rules/git/general.mdc - **Never merge a PR without a converged code review.** A code review must have been run on the PR's final diff and report **no errors** — 0 Critical + 0 Moderate findings (Minor does not block). This is the hard merge gate from `@rules/git/general.mdc` *Merging*; it is mandatory on every merge and is verified in step 2 below. - Never merge PRs with conflicts - Never merge PRs with failing CI (unless explicitly instructed) - Never bypass required approvals or protections - The only tolerated CI failure is a **GitHub Actions billing / account-limit error** when the merge is **explicitly requested** (see *GitHub Actions billing exception* below). Any other failure — real test failure, lint, static analysis — still blocks. --- ## Execution ### 1. Load PRs - Identify candidate PRs ready for merge - For each candidate, load PR context by running `skills/code-review-github/scripts/load-issue.sh <NUMBER|URL>` — the single deterministic entry point. Never call `gh pr view`, `gh pr checks`, or `gh api /repos/.../pulls/...` directly. Read `isDraft`, `mergeable`, `mergeStateStatus`, `reviewDecision`, and `statusCheckRollup[]` off the resulting JSON document. - If the script is unavailable (missing tool, exit code 2/3) fall back to the GitHub MCP server. ### 2. Pre-checks (must all pass) For each PR, derive the verdict from the JSON document loaded