ot-merge-buddy

Classifies open pull requests by merge readiness from labels, reviews, CI, and mergeability.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams with many open pull requests lose track of which ones can actually merge. This Skill scans the entire PR queue through the configured tracker, evaluates every merge gate, and reports exactly what can ship now, what is close, and what is blocked — without merging or modifying anything. ## Core Features & Use Cases - Merge readiness classification: Evaluates review approval, required CI checks, merge conflicts, merge state, and blocking labels for every non-draft PR, then sorts results into ready, almost ready, and blocked buckets. - QA gate enforcement: When the configured QA gate is on, a PR labeled needs-qa cannot be classified as ready until it carries qa-approved, with skip-qa as the explicit opt-out. - Read-only reporting: Produces a queue report with counts, one row per PR with its next action, and never merges, edits, comments on, or labels anything. - Use Case: Before a release, ask the agent to scan the repo's open PRs; it returns a table showing three PRs ready to merge (oldest first), two almost ready pending only CI, and four blocked with the exact blocker for each. ## Quick Start Ask the agent to scan all open pull requests and report which ones are ready to merge right now.

Frequently Asked Questions about ot-merge-buddy

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

FAQPage Schema
How do I check which open pull requests are ready to merge?▼

Run the merge scan to list open PRs from the configured tracker and evaluate each against review approval, required CI checks, merge conflicts, and blocking labels. The report sorts ready PRs oldest first and shows the next action for every other PR.

What merge gates does a pull request readiness check evaluate?▼

The gates are an APPROVED review decision, green required CI checks, no merge conflicts, a clean merge state, and absence of blocking labels like changes-requested, qa-failed, blocked, do-not-merge, or in-progress. Pending CI alone classifies a PR as almost ready rather than blocked.

Does this skill merge pull requests automatically?▼

No, it is strictly read-only and never merges, edits, comments on, or labels anything. When you pick a PR to ship, it hands off to the ot-approve-merge-pr skill, which re-checks the same gates before merging.

How does the QA approval gate affect merge readiness?▼

When qaGate is enabled in the configuration, a PR labeled needs-qa must already carry qa-approved to be classified as ready, even if every other check is green. A PR with skip-qa is exempt, and when qaGate is off the missing QA sign-off is only advisory.

Can the merge scan work when labels are disabled?▼

Yes. When labels.enabled is false in the configuration, all label-based gates are skipped and classification relies on reviews, CI, and mergeability alone. The report header discloses that label gates were disabled.

Why are some pull requests missing from the merge readiness report?▼

Draft PRs are skipped entirely, and PRs labeled in-progress are skipped because another automated skill is still working on them. In-progress PRs appear only if you ask for a full inventory.