How do I install the Merge Prs skill?

Run npx skillmds@latest add blauwtje/merge-prs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Merge Prs safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Merge Prs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Merge Prs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Merge Prs?

blauwtje (@blauwtje) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Merge Prs by blauwtje — Agent Skill

Name: Merge Prs
Rating: 4.5 (4 reviews)
Author: blauwtje

Merge Prs

Review and merge the open pull requests of this repository one at a time behind hard gates read from the GitHub API. Use when the user asks to merge open or listed PRs. Not for reviewing code, for a PR the user did not name or list, or for anything that deletes a branch.

blauwtje Updated Sep 22, 2026

File contents

Merge pull requests, one at a time

Merge only what the API proves mergeable, one PR per step, and re-read the API before every claim. The enemy is a merge script that remembers a CI status instead of re-reading it: one such run auto-closed a stacked PR and reported a merge that never happened. The overcorrection is batching: several merges in one command hide which gate failed for which PR.

Invoking this skill authorizes the merges it performs on the PRs the user named, or on every open PR when the user said so; it authorizes nothing else.

Steps

List. gh pr list --json number,title,baseRefName,headRefName. Keep the user's order when they named PRs; otherwise take the list order. Print the table before touching anything.
Gate, per PR, from the API. Run gh pr view <n> --json number,title,mergeable,mergeStateStatus,statusCheckRollup,baseRefName,headRefName,reviewDecision --jq '{number,title,mergeable,mergeStateStatus,reviewDecision,baseRefName,headRefName,checks:[.statusCheckRollup[]|{name,context,conclusion,state}]}' and print that JSON; the sliced checks keep a PR with many workflows under one screen of output. Merge only when mergeStateStatus is CLEAN and every entry in statusCheckRollup has conclusion SUCCESS or state SUCCESS. BLOCKED, BEHIND, DIRTY, UNSTABLE, UNKNOWN, a pending check, or a CHANGES_REQUESTED review is a stop for that PR: report it and continue with the next PR. Never read the status from memory or from an earlier step.
Stack check. A PR is a base when another open PR's baseRefName equals its headRefName. Merge bases before the PRs stacked on them, and never pass --delete-branch for a PR that is a base: GitHub closes the stacked PR when its base branch disappears. Say which PRs this applies to.
Merge one. gh pr merge <n> --squash (or the repository's documented merge method) without --delete-branch. Branch deletion is a separate, explicitly authorized step and never runs here.
Re-verify. gh pr view <n> --json state,mergedAt must show state MERGED. Report a merge only after that read; otherwise report the PR as not merged with the JSON that says so. Stacked PRs then need a fresh gate, since their base just moved.
Report. One table: PR, gate result, merged yes/no, blocking reason. When git worktree list names a worktree on a merged PR's branch, add one line naming git worktree remove <path> for the user to run; this skill removes nothing. Stop and report as soon as anything is ambiguous. Do not retry a failed merge unchanged.

Judgment

API JSON read in this step outranks any earlier read or remembered status.
A stop for one PR outranks finishing the list: report it, never force, never relax a gate.
The user's authorization outranks this skill's defaults, except the --delete-branch and git branch -D prohibitions, which need their own explicit instruction naming the branch.

---name: merge-prsdescription: Review and merge the open pull requests of this repository one at a time behind hard gates read from the GitHub API. Use when the user asks to merge open or listed PRs. Not for reviewing code, for a PR the user did not name or list, or for anything that deletes a branch.---# Merge pull requests, one at a timeMerge only what the API proves mergeable, one PR per step, and re-read the APIbefore every claim. The enemy is a merge script that remembers a CI statusinstead of re-reading it: one such run auto-closed a stacked PR and reported amerge that never happened. The overcorrection is batching: several merges inone command hide which gate failed for which PR.Invoking this skill authorizes the merges it performs on the PRs the usernamed, or on every open PR when the user said so; it authorizes nothing else.## Steps1. **List.** `gh pr list --json number,title,baseRefName,headRefName`. Keep the user's order when they named PRs; otherwise take the list order. Print the table before touching anything.2. **Gate, per PR, from the API.** Run `gh pr view <n> --json number,title,mergeable,mergeStateStatus,statusCheckRollup,baseRefName,headRefName,reviewDecision --jq '{number,title,mergeable,mergeStateStatus,reviewDecision,baseRefName,headRefName,checks:[.statusCheckRollup[]|{name,context,conclusion,state}]}'` and print that JSON; the sliced checks keep a PR with many workflows under one screen of output. Merge only when `mergeStateStatus` is `CLEAN` and every entry in `statusCheckRollup` has `conclusion` `SUCCESS` or `state` `SUCCESS`. `BLOCKED`, `BEHIND`, `DIRTY`, `UNSTABLE`, `UNKNOWN`, a pending check, or a `CHANGES_REQUESTED` review is a stop for that PR: report it and continue with the next PR. Never read the status from memory or from an earlier step.3. **Stack check.** A PR is a base when another open PR's `baseRefName` equals its `headRefName`. Merge bases before the PRs stacked on them, and never pass `--delete-branch` for a PR that is a base: GitHub closes the stacked PR when its base branch disappears. Say which PRs this applies to.4. **Merge one.** `gh pr merge <n> --squash` (or the repository's documented merge method) without `--delete-branch`. Branch deletion is a separate, explicitly authorized step and never runs here.5. **Re-verify.** `gh pr view <n> --json state,mergedAt` must show `state` `MERGED`. Report a merge only after that read; otherwise report the PR as not merged with the JSON that says so. Stacked PRs then need a fresh gate, since their base just moved.6. **Report.** One table: PR, gate result, merged yes/no, blocking reason. When `git worktree list` names a worktree on a merged PR's branch, add one line naming `git worktree remove <path>` for the user to run; this skill removes nothing. Stop and report as soon as anything is ambiguous. Do not retry a failed merge unchanged.## Judgment- API JSON read in this step outranks any earlier read or remembered status.- A stop for one PR outranks finishing the list: report it, never force, never relax a gate.- The user's authorization outranks this skill's defaults, except the `--delete-branch` and `git branch -D` prohibitions, which need their own explicit instruction naming the branch.

Frequently asked questions