ha-merge-queue

Name: ha-merge-queue
Availability: InStock
Author: Home Assistant

Identify Home Assistant pull requests ready to merge by verifying CI, reviews, and conflicts.

90.2k|38.4k|Updated Sep 17, 2013

Search Tags:#triage #code-review #pull-request #home-assistant #gitHub #ci-verification #merge-queue

Ready to run

npx skills add https://github.com/home-assistant/core --skill ha-merge-queue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ha-merge-queue
Source: https://github.com/home-assistant/core/tree/main/.claude/skills/ha-merge-queue
Command: npx skills add https://github.com/home-assistant/core --skill ha-merge-queue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers of the home-assistant/core repository face a flood of open pull requests and need a reliable way to surface the ones that are genuinely ready to merge, separating them from near-misses that need a single specific nudge.

Core Features & Use Cases

Six-condition PR verification: Checks merge-gate statuses, GitHub Actions check runs, merge conflicts, review submissions, review threads, and peer-review checklist participation.
Ranked shortlist with near-miss reporting: Produces a ranked list of clean PRs and a separate list of near-misses, each annotated with the one action that unblocks it.
Use Case: A maintainer asks for the top 10 quick-win PRs to merge during a triage session and receives a ranked list with explicit blocking states and peer-review participation flags.

Quick Start

Find the top 10 open pull requests in home-assistant/core that are ready to merge right now.

Frequently Asked Questions about ha-merge-queue

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

FAQPage Schema

How do I find pull requests ready to merge in home-assistant/core?▼

Search open PRs excluding drafts and stale labels, then verify each candidate against merge-gate statuses, check runs, mergeable_state, review submissions, and review threads. A PR passes only when all six conditions are satisfied.

What does mergeable_state mean for a GitHub pull request?▼

mergeable_state indicates whether the PR can be merged: clean means ready, blocked means a branch-protection requirement is unmet, behind means the base branch moved, unstable means a non-required check failed, and dirty means there are merge conflicts.

Why does a PR show green CI but still fail the merge gate?▼

Combined commit statuses do not cover GitHub Actions check runs. A PR can show green status while a test job is failing, queued, or still in progress, so check runs must be fetched and verified independently.

Does a resolved review thread withdraw a CHANGES_REQUESTED review?▼

No. Resolving an inline thread does not withdraw the review submission. A standing CHANGES_REQUESTED from a reviewer disqualifies the PR until that reviewer submits a later APPROVED review.

When should I not trust the GitHub search status filter?▼

The search index lags reality by hours, so status filters are rough approximations only. Always verify finalists with per-PR API calls and paginate check runs, reviews, and threads to completion before deciding.