What problem does it solve? A PR can show a "merged" badge while its changes never actually reach the default branch — stacked PRs merged before GitHub retargets them, pushes onto already-merged branches, or merges against stale bases. This Skill detects those orphaned merges and re-lands the lost work on a fresh branch cut from the current default branch. ## Core Features & Use Cases - Orphan Detection: Verify with git merge-base --is-ancestor and content checks (git cat-file, git show) whether a merged PR's head and files actually exist on main. - Damage Assessment: Measure staleness with git log and git diff --stat to determine whether merging the old branch would revert newer work. - Faithful Re-landing: Reconstruct the PR's exact diff with git diff <base> <head> | git apply --3way onto a branch cut from current main, then verify fidelity against the original head and run the test suite. - Use Case: You merged a stacked PR one minute after its base, both show "merged", but a fresh clone lacks the feature. This Skill confirms the orphan, re-lands the diff on a new branch, and opens a replacement PR with the evidence reviewers need. ## Quick Start Ask the assistant to check whether PR #245's changes actually landed on main and re-land them if they are missing.
