What problem does it solve? Merging a pull request safely requires checking review state, CI status, labels, and QA sign-off before clicking merge, and doing this by hand is error-prone. This Skill automates the approve-and-merge flow for a single PR while refusing to merge past hard blocks like qa-failed, do-not-merge, or an unsatisfied QA gate. ## Core Features & Use Cases - Gate-checked merging: Submits an approving review and squash-merges a PR only after validating state, draft status, conflicts, blocking labels, and the QA gate (needs-qa requires qa-approved). - Fixable-blocker routing: When CI fails or conflicts exist, it routes to the om-auto-fix-pr skill (--ci-only for failing checks, full loop for conflicts or review feedback) instead of dead-ending. - Optional follow-up issues: Files a follow-up issue after a successful merge, either from free-text asks or by handing off a PR/comment link to om-followup-issue-from-pr. - Use Case: A reviewer says "approve and merge PR 2805 with follow-up: extract the data-scoping check into a shared helper" — the Skill verifies gates, approves, squash-merges, and files the follow-up issue assigned to the PR author. ## Quick Start Ask the agent to approve and merge PR 2805, optionally adding a follow-up note to file as an issue after the merge.
