What problem does it solve? Dependent changes split across multiple pull requests become dangerous when a lower layer merges, is retargeted, or is rewritten while child PRs remain open. This Skill enforces a strict safety doctrine for stacked PRs so rebases, retargets, and branch deletions never orphan child branches or lose commits. ## Core Features & Use Cases - Boundary preservation: Saves branch, tip, PR number, base/head names, and exact remote OIDs for every layer before any mutation, invalidating candidates on any drift. - Safe restacking: Uses git rebase --onto <new-parent> <saved-old-parent> <child> to replay only each child's commits, cascading from the parent outward. - Leased force-push and deletion: Pushes and deletes remote branches only with --force-with-lease bound to the exact saved remote OID, treating lease failures as stops rather than retries. - Use Case: After PR 1 of a three-layer stack merges, retarget PR 2 to main, rebase PR 3 onto the new parent, re-gate each layer, and delete the merged branch only after verifying no open PR uses it as a base. ## Quick Start Use the stacked-prs skill to restack my open PR chain after the bottom PR merged, retargeting each child and force-pushing with saved-OID leases.
