What problem does it solve? Merging pull requests safely requires checking review state, CI status, QA sign-off, and blocking labels — a manual process that is easy to get wrong. This Skill automates the approve-and-merge flow for a single PR while refusing to merge when quality gates forbid it. ## Core Features & Use Cases - Gate-enforced merging: Submits an approving review and squash-merges a PR only after verifying hard label blocks (qa-failed, do-not-merge, blocked), the QA approval gate, and QA head SHA freshness against the current PR head. - Fixable-blocker routing: When CI fails or conflicts exist, it routes to om-auto-fix-pr (with --ci-only or the full loop) instead of dead-ending, then merges once the PR is green. - Optional follow-up issues: Files a follow-up issue after a successful merge, with assignee and labels inferred from the PR, or hands off PR/comment links to om-followup-issue-from-pr. - Use Case: A reviewer says "approve and merge PR 2805 with follow-up: extract the shared helper" — the Skill verifies the QA gate, approves, squash-merges, and files the follow-up issue referencing the merged PR. ## Quick Start Ask the agent to approve and merge PR 123, optionally adding a follow-up note to file as an issue after the merge.
