← ClaudeAtlas

work-consolidate-supersede-branches-prslisted

Consolidate several branches (and their PRs, if any) plus the latest base into ONE new branch that supersedes them all — merge each onto the others so every branch's changes propagate BOTH ways, reverse-merge the current base the same way, resolve every conflict for behaviour, build any additional asks on top, and hand it back as a superseding draft PR (or a bare branch) that closes the originals. Never touches master/the base; leaves the new PR draft. Use for "consolidate these branches/PRs into one", "supersede
skowalskidev/dotclaude · ★ 2 · Data & Documents · score 75
Install: claude install-skill skowalskidev/dotclaude
# Consolidate + supersede several branches/PRs into one The task shape: N branches (each maybe carrying an open PR) overlap, plus extra feature asks, and become ONE new branch that supersedes them all. Every branch's changes must survive onto every other (both ways), the base is brought current (reverse-merge master/the base), the extra asks are built on top, and it ships back as a draft PR — or a bare branch when no PR is wanted — that closes the originals. The base is never touched. This is a SPINE. It composes the parts below at each stage — invoke each, never restate it: `/sk:plan-stable-persistent-dynamic-complete-full-plan`, `/sk:ship-check-merge-readiness`, `/sk:work-full-detailed-workflow`, `/sk:ship-full-detailed-workflow`, `/sk:meta-dotclaude-copilot-start-here-for-any-task`. Read `references/parallelization.md` for the fan-out craft and `references/git-pr-deploy.md` for the branch/PR/deploy rules. ## Step 0 — Establish the inputs, confirm the two forks, never touch the base - **List every input** — each branch's head ref, its PR if one exists (`gh pr view` for the ticket list + body), the additional feature asks, and the base (`git rev-parse origin/master`). - **Confirm the two forks that waste the most work if guessed, in ONE AskUserQuestion up front:** the merge TOPOLOGY (a NEW branch off one head with the rest merged in), and whether to CLOSE the superseded PRs. - **NEVER merge, push, or write the base.** The new branch is the only ref you push, and only