Verify a merged PR landed by content without orphaned late commits, post its `Review record` comment on the merged PR, and plan cleanup only when explicitly requested. Use after a PR merges into main.
94%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Medium
Suggest reviewing before use
Follow Landed and the detailed procedure:
<pr>. Run npm run workflow:lifecycle -- --phase landed --write-evidence, then once GitHub read access is authorized run gh pr view <pr> --json state,mergeCommit,mergedAt and verify state is MERGED with non-null mergeCommit and mergedAt.origin/main, inspect git rev-list --parents -n 1 <merge-commit>, and verify by content: git merge-base --is-ancestor <your-branch-tip> <merge-commit>^2 plus git show --remerge-diff <merge-commit> for a two-parent merge; git diff --stat <squash-commit> <your-branch-tip> (or git patch-id --stable comparing git diff <squash-commit>^ <squash-commit> with git diff $(git merge-base <squash-commit>^ <your-branch-tip>) <your-branch-tip> when behind main) for a squash merge.git branch -D require an explicit cleanup request; empty content proof does not itself authorize deletion.Review record comment on the merged PR with scope prlanded, per Records.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.