pr-gatelisted

Validate a pull request end to end — work out what it actually changes and who it breaks, diagnose and fix a red pipeline, triage agent review comments (fix the valid ones, reply to and resolve the rest), judge whether it is genuinely ready, and merge it when asked. Use this whenever the user points at a PR (a number, a URL, "this PR", a Renovate/Dependabot bump) and wants to know whether it is safe, why a check is failing, whether it can be merged, or wants it merged. Use it for inbound PRs you did not write, dependency bumps, and any "is this ready to merge", "can you merge it", "fix the CI on this PR", "why is this check red", "address the review comments", or "does this break anything" request. For deploying and canary-verifying your own freshly shipped PR, use land-and-deploy instead; for a line-by-line code critique with no merge decision, use code-review.
Max-Levitskiy/skills · ★ 0 · AI & Automation · score 66

Install: claude install-skill Max-Levitskiy/skills

# PR Gate A PR is a proposal. Your job is to turn it into a verdict backed by evidence, and then — only if asked — to act on that verdict. The failure mode this skill exists to prevent is the confident wrong answer in either direction: blocking a safe change because a changelog sounded scary, or merging a breaking one because the checkmarks were green. Both come from reasoning about what a change *says* it does instead of what it *does*. ## Settle which PR, before anything else This skill operates on one specific PR, and everything below is wasted if it runs against the wrong one. Resolve it first: - **The user named one** — a number, a URL, or a branch. Use it. - **They didn't, but the current branch has an open PR.** Use that, and say in one line which one you picked, so a wrong guess is visible and cheap to correct rather than discovered three minutes into a validation. - **Neither.** Do not guess, and do not quietly validate the first open PR you find. List the open PRs and **ask the user which one to process** — use `AskUserQuestion` so the choice is one keystroke rather than a typed reply. `pr-facts.sh` does this resolution for you: given no argument it falls back to the current branch, and when even that fails it prints the open PRs and exits **2**, which is your cue to ask rather than proceed. Exit **3** means the repo has no open PRs at all — say so instead of hunting. When the list is long, order the options by what the user's question implies: most r