Verify a merged PR actually landed correctly in this repo and clean up after it. Use right after a PR merges (especially with auto-merge) to confirm the merge commit, or for older PRs the squashed commit, matches your branch by content, catch late commits that were orphaned by the auto-merge race, and post its review record and update memory.
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
The rules for proving a merge carried the work — decide squash versus merge commit by parent count, the right comparison for each, late commits, and cleanup — are in Landed. This skill is the Claude Code procedure for applying them. Owner-merge PRs are merged by Josh, not by agents (Merge authority).
The user's explicit request to verify a named PR authorizes the read-only PR lookup for that target. Otherwise ask before GitHub access; never infer provider authority merely from local branch state.
gh pr view <pr> --json state,mergeCommit,mergedAt → MERGED.git fetch --quiet origin main, read the
parent count with git rev-list --parents -n 1 <merge-commit>, then run the comparison
Landed names for that shape: for a
two-parent merge, run git merge-base --is-ancestor <your-branch-tip> <merge-commit>^2
and git show --remerge-diff <merge-commit>; for a squash, run the two-dot
git diff --stat <squash-commit> <your-branch-tip> (never three-dot). Any unexplained
remaining line is work that did not land — investigate before deleting anything.
If the branch was behind main when it merged (always true for a merge-queue merge), that
two-dot diff also shows main's changes: compare the explicit PR diff
git diff <squash-commit>^ <squash-commit> | git patch-id --stable with
git diff $(git merge-base <squash-commit>^ <your-branch-tip>) <your-branch-tip> | git patch-id --stable,
exactly as Landed describes.git branch -D are destructive and require an explicit cleanup request. Resolve
and validate the exact worktree path from a different worktree, then report the commands or run
them only within that authorization. For squash-merged branches, explain why -d refuses and
why -D would be needed; empty content proof is necessary but does not itself authorize deletion.Review record comment on the merged PR
with the branch, the merged commit's full 40-character SHA, scope prlanded, the outcome and
the checks run, plus any relevant memory note.Review record at that head for the same scope.BigSimmo/PsychSift
0d5a97a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.