What problem does it solve? Merging pull requests without verifying that the reviewed and promoted commit matches the current remote head risks shipping unreviewed or drifted code. This Skill enforces a guarded merge step inside the Agentic SDLC workflow so only the exact reviewed SHA is merged after all readiness gates pass. ## Core Features & Use Cases - SHA-Verified Merge: Requires the local clean HEAD, promoted SHA, reviewed PR head, and current remote PR head to be identical before merging. - Canonical Merge Command: Builds one exact gh pr merge command with --match-head-commit and an explicit strategy, rejecting admin bypass, branch deletion, and compound commands. - Short-Lived Authorization: Writes a scoped merge-authorization.json with expiry, expected head, base branch, and readiness statuses immediately before execution. - Use Case: After an Agentic SDLC run completes review and UAT, the coordinator invokes this Skill to merge the PR only when checks, reviews, branch state, and UAT evidence all pass. ## Quick Start Ask the agent to merge a specific pull request by number or URL only after confirming the promoted and reviewed SHA matches the current remote head.