ot-approve-merge-pr

Approves and squash-merges a GitHub pull request while enforcing QA gate and label blocks.

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/triage-software/skills --skill ot-approve-merge-pr-triage-software
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ot-approve-merge-pr
Source: https://github.com/triage-software/skills/tree/main/skills/ot-approve-merge-pr
Command: npx skills add https://github.com/triage-software/skills --skill ot-approve-merge-pr-triage-software

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Merging a pull request safely requires checking review state, CI status, QA approval, and blocking labels before acting. This Skill automates that final step: given only a PR number, it submits an approving review and squash-merges the PR, but refuses whenever the QA gate or a hard-blocking label forbids it. ## Core Features & Use Cases - Gate-enforced merging: Refuses to merge PRs labeled qa-failed, do-not-merge, or blocked, and enforces the needs-qa/qa-approved QA gate when enabled in the repo config. - Fixable-blocker routing: Routes failing CI to ot-auto-fix-pr --ci-only and conflicts or unresolved review feedback to the full ot-auto-fix-pr loop instead of dead-ending. - Optional follow-up issues: Files a tracking issue after a successful merge, with assignee and labels inferred from the PR, or hands off PR/comment links to ot-followup-issue-from-pr. - Use Case: A reviewer says "approve and merge PR 2805, and add a follow-up to extract the shared helper" — the Skill verifies gates, approves, squash-merges, and files the follow-up issue referencing the merged PR. ## 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.

Frequently Asked Questions about ot-approve-merge-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I approve and merge a GitHub PR with one command?▼

Provide the PR number with intent to merge, such as "approve and merge PR 123". The Skill submits an approving review, verifies merge gates and labels, then squash-merges through the configured tracker operations.

What happens when a PR has failing CI checks before merging?▼

The merge is refused and the blocker is reported. The Skill offers to route the PR to ot-auto-fix-pr with the --ci-only flag, which fixes failing checks, after which the merge can be retried once checks are green.

Can a PR merge without QA approval when the QA gate is enabled?▼

No. When qaGate is true, a PR labeled needs-qa without qa-approved is not mergeable even with green CI and reviews. The gate is satisfied by manual QA, the self-QA exception with proof, or a skip-qa label for low-risk changes.

Which labels block a pull request from being merged?▼

The labels qa-failed, do-not-merge, and blocked are hard blocks that always refuse the merge. An active qa pipeline label also stops the merge because manual testing is in progress, and needs-qa plus skip-qa together requires user clarification.

Does it support merge queues or auto-merge when checks are pending?▼

Yes. When required checks are still running or the user asks to merge once checks pass, the Skill requests the tracker descriptor's merge-automatically-once-checks-pass option instead of a plain merge, letting branch protection enforce the gate.

When should I not use this Skill to merge a PR?▼

Do not use it to bypass humans: hard label blocks and the QA gate require manual resolution and never route to automation. Conflicting or failing PRs should go through ot-auto-fix-pr first rather than being force-merged.