What problem does it solve? Merging a pull request involves resolving the right merge-commit title and body from scattered sources (change-record blocks, commits, labels, PR titles), validating PR state, and choosing strategy and branch-deletion behavior. This Skill orchestrates that entire flow with an approval gate so nothing incorrect gets published to a protected default branch. ## Core Features & Use Cases - Merge-commit resolution: Runs describe-change.mjs resolve-merge to derive the effective record, merge title, and body from the PR's change-record block, commits, labels, and title, with CLI overrides for scope, type, and breaking markers. - Approval gate with defect handling: Settles missing-type and policy-violation defects through structured questions, renders the proposed title, body, strategy, and deletion plan, and requires explicit user confirmation naming every destructive side effect. - Platform delegation: Dispatches the actual merge to merge-gh-pr (GitHub) or merge-bb-pr (Bitbucket), re-reading the PR after approval to catch edits made while the gate was pending. - Use Case: After finishing a feature branch and opening a PR, invoke this Skill to compose a conventional-commit-style merge message, confirm the squash strategy and remote branch deletion, and merge through the GitHub CLI without hand-writing the commit text. ## Quick Start Ask the agent to merge the pull request for the current branch, optionally passing flags like --pr 42, --strategy squash, or --delete remote.
