What problem does it solve? After a branch is attested and its pull request is open, the base branch can move forward or the PR can land without any signal to the session. This Skill performs a single stateless check that tells you whether the merge target advanced, the PR merged or closed, or the branch is still current, so stale attestations never slip through unnoticed. ## Core Features & Use Cases - One-shot merge-target check: Runs scripts/check-merge.sh once and classifies the result via exit codes — contained (0), target advanced (10), PR merged (20), PR closed (21), or hard error (1). - Base-aware resolution: Resolves the merge target from the PR's actual base branch rather than assuming main, so promotion branches and long-lived feature branches are handled correctly. - Squash comment reconciliation: While the PR is open, invokes the squash-message skill in update-only mode to edit the stale 'Proposed squash title/body:' PR comment in place when the branch has drifted. - Use Case: You return to a session whose branch was attested yesterday. Run the check to learn that origin/main advanced three commits, hand control back to the enclosing finalize flow to re-verify, and have the squash message comment refreshed automatically. ## Quick Start Ask the assistant to run /check-merge on the current branch to see whether the merge target moved since the branch was last attested.