CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prlanded

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.

Quality

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

prlanded — confirm a merge landed and tidy up

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).

Steps

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.

  1. Confirm the merge: gh pr view <pr> --json state,mergeCommit,mergedAt → MERGED.
  2. Verify by content, branching on the merge shape. 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.
  3. Check for orphaned late commits pushed after auto-merge was armed; if missing, fix-forward with a new PR — do not force-push.
  4. Prepare cleanup only after the content diff is empty. Worktree removal, remote branch deletion, and 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.
  5. Record per Records: post one 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.

Notes

  • Do not re-review a PR whose comments already hold a Review record at that head for the same scope.
  • If the content diff is non-empty and you are unsure why, stop and report rather than deleting anything.
Repository

BigSimmo/PsychSift

Path

.claude/skills/prlanded/SKILL.md

Last updated
First committed

Is this your skill?

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.