What problem does it solve? Merging a pull request safely requires checking its state, reviews, conflicts, and branch sync before executing, then recording what happened. This Skill automates that guarded merge flow through the GitHub CLI so merges fail closed instead of landing broken or unreviewed code. ## Core Features & Use Cases - Pre-merge validation: Refuses to merge when the PR is closed, draft, conflicting, blocked, or has unresolved review requirements, failing closed when state cannot be determined. - Strategy-aware merging: Maps squash, merge, and rebase strategies to the correct gh pr merge flags, verifies the merge-commit body file before publishing, and handles branch deletion per the requested deletion strategy. - Merge artifact recording: Captures the merge commit SHA, URL, and timestamp, then saves a structured merge artifact into the ticket directory for traceability. - Use Case: An orchestrating workflow calls this delegate with a fully-resolved PR number, title, body, and strategy; it validates PR #42 is open and approved, squash-merges it with the approved commit message, deletes the remote branch, and writes a merge record to the ticket directory. ## Quick Start Ask the agent to merge pull request 42 on GitHub using the squash strategy with the prepared title and body, then save the merge artifact to the ticket directory.
