om-merge-buddy

Classify open pull requests by merge readiness from reviews, CI checks, and labels.

1|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/tkogut/agents-os-core --skill om-merge-buddy-tkogut
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: om-merge-buddy
Source: https://github.com/tkogut/agents-os-core/tree/main/global_skills/om-merge-buddy
Command: npx skills add https://github.com/tkogut/agents-os-core --skill om-merge-buddy-tkogut

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 every open PR through the configured tracker, evaluates review approvals, CI status, mergeability, and label-based gates, then reports which PRs are ready to merge, which are almost ready, and which are blocked. ## Core Features & Use Cases - Merge readiness triage: Fetches open PRs and evaluates gates including review decision, required CI checks, merge conflicts, blocking labels, and QA sign-off status. - QA gate enforcement: When the QA gate is enabled, verifies that PRs needing QA carry an approval label and that the QA-tested head commit matches the current head. - Read-only reporting: Produces a sorted merge queue report with one row per PR showing its state and next action, without ever merging, editing, commenting, or labeling. - Use Case: Before a release, ask for a merge queue scan to instantly see that three PRs are ready to merge, two are waiting only on pending CI, and one is blocked by unresolved conflicts. ## Quick Start Scan all open pull requests and tell me which ones are ready to merge right now.

Frequently Asked Questions about om-merge-buddy

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

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

Run a merge queue scan that fetches all open PRs and evaluates review approval, required CI checks, merge conflicts, and blocking labels. The report sorts ready PRs oldest first and lists each PR's state with its next action.

What gates determine pull request merge readiness?▼

A PR is ready when the review decision is approved, required CI checks are green, there are no merge conflicts, and no blocking labels like changes-requested, do-not-merge, or qa-failed are present. When the QA gate is enabled, PRs needing QA must also carry a QA approval matching the current head commit.

Does this skill merge pull requests automatically?▼

No, it is strictly read-only and only classifies and reports merge readiness. When you pick a PR to ship, it hands off to a separate approval skill that re-checks the same gates before merging.

Can merge triage work when labels are disabled?▼

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

Why is a PR with pending CI classified as almost ready instead of blocked?▼

Pending CI is treated as a blocker, but when it is the only missing gate the PR is classified as almost ready because merging requires genuinely green checks. No local validation run substitutes for required CI results.