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, evaluates review approvals, CI checks, merge conflicts, and blocking labels, then reports exactly which PRs are ready to merge, which are almost ready, and which are blocked. ## Core Features & Use Cases - Merge readiness triage: Fetches open PRs via the configured tracker and evaluates gates including review approval, required CI checks, mergeable state, and blocking labels such as changes-requested, qa-failed, blocked, and do-not-merge. - QA gate enforcement: When the qaGate config is enabled, a needs-qa PR without qa-approved is never classified as ready, while skip-qa acts as an explicit opt-out. - Structured report: Produces a three-section Markdown report (Ready to Merge, Almost Ready, Blocked) where every row explains in full sentences which gates pass or fail and what would move the PR forward. - Use Case: Before a release, run the skill to get a read-only inventory showing that PR #123 is mergeable, PR #456 only waits on pending CI, and PR #789 is blocked by conflicts and a changes-requested review. ## Quick Start Ask the agent to run the merge buddy skill and report which open pull requests can merge right now.
