Merge the open PRs Snapshot the open PRs. That list is the work set. Merge each PR through the forge, one at a time, in an order that keeps later PRs updateable onto the default branch. Do not assemble independent PRs into a stack or replace the work set with one combined PR. Standing rules: The work set does not grow. A PR opened after the snapshot is ignored. After every merge, compare remaining open PRs to the work set; never merge extras. Repository merge policy controls freshness. After each merge, recheck the remaining PRs. Update a branch only for a conflict, a changed dependency, or the repository's explicit freshness requirement. A base move alone does not invalidate passing checks on an unchanged PR head. Every PR lands through the forge. Never merge into a local default branch and push, and never push straight to the default branch. Do local git work only on the PRs' own branches, in a temporary worktree you remove afterwards. 1. Snapshot the work set Read every page. If the user named specific PRs, those are the work set; otherwise every open PR is. Record numbers, head SHAs, and head branches. For anything but a single obvious PR, build a file overlap map: An unready PR (draft, requested changes) stays in the work set. Make it mergeable; do not drop it, and do not merge over unanswered requested changes without user direction. If the work set is empty, stop. 2. Choose the merge order Files disjoint PRs cannot conflict textually in any order, so order for semantics and verifiability. In priority order: Small, isolated PRs first (config tweaks, dependency bumps, tooling that helps verify later PRs). Foundational before dependent: when one PR calls what another adds, merge the dependency first. Shared state PRs last: a version constant, migration number, or checked in generated artifact compounds with everything already landed. Otherwise by blast radius, smallest first. If a PR's base is another work set PR, merge the parent first. An existing base chain is evidence for that order. A user stated order wins. State the order and a one line reason per PR before you start. 3. Know the gate Pass the repo's merge method explicitly on gh pr merge . Rulesets and classic protection are separate; check both for required checks, required reviews, and strict up to date policy. 4. Merge each PR Work in a temporary worktree. For each PR in order: 1. Fetch. Record the default branch tip. 2. If this PR's base is another work set PR, wait until that parent has merged. Retarget with gh pr edit <n base <default branch when GitHub has not already. 3. Check whether this PR needs a base update under the repository's policy. Resolve conflicts on its branch with [resolve pr conflicts](../resolve pr conflicts/SKILL.md). Confirm isCrossRepository and maintainerCanModify match the remote you will update. Get explicit approval before rewriting a branch you do not own unless already authorized, and disclose every rewrite. 4. Push any needed update. Drafts block: gh pr ready first, with user direction where the draft was deliberate. 5. Verify with the repo's own checks on this PR: build, format, lint, and the tests for its blast radius. Wait until every required check on this PR is green using [babysit](../babysit/SKILL.md). If the PR cannot be made mergeable on the current default, stop and ask. 6. Re read the head SHA, mergeability, and repository gates. A new head needs its own passing checks. A base move needs another update only when the repository policy or a new conflict requires it. Then: A merge queue queues the PR and picks its own method; wait until it lands before starting the next PR. If a teammate pushes to a work set branch, inspect and preserve their changes, coordinate when possible, and verify the new head. Ask only if ownership or the intended resolution is unclear. A closed PR is no longer mergeable: report it and continue with independent PRs. If someone merges a work set PR, continue with the remaining PRs. admin only with explicit approval, disclosed in the report. After the last merge, verify the repository's required integration result on the default branch. Use its CI run when that supplies the required evidence; run additional local checks for uncovered risks. Remove the worktree. 5. Report 1. Work set PRs, PRs ignored as later arrivals, and whether files overlapped. 2. Merge order with a reason each. Any work set PR not merged, and why. 3. Conflicts resolved, branches rewritten, any bypass. 4. Default branch moves and what you did about them. 5. What you ran and what passed, including on the final default branch. 6. Final default branch SHA and remaining open PRs. If the request chains a release, use $tag release after CI is green on the merged commit.

merge-open-prs