Home Assistant is open-source home automation software that lets people control devices and actions locally through a modular system. It is used by home-automation enthusiasts and DIY users, often on a Raspberry Pi or local server; the catalogue entries support operating or developing its integrations and codebase.
Borrowing it
Nothing to install: this file belongs to home-assistant/core. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/home-assistant/core/dev/.claude/skills/ha-merge-queue/SKILL.mdgit clone --depth 1 https://github.com/home-assistant/coreWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/home-assistant/core/ha-merge-queue)<a href="https://agentmods.dev/skills/home-assistant/core/ha-merge-queue"><img src="https://agentmods.dev/badge/skills/home-assistant/core/ha-merge-queue/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/home-assistant/core/ha-merge-queue"><img src="https://agentmods.dev/badge/skills/home-assistant/core/ha-merge-queue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00072 | $0.01886 |
| Opus 5.5 | $0.00029 | $0.00754 |
| Sonnet 5.5 | $0.00014 | $0.00377 |
| Haiku 4.5 | $0.00007 | $0.00189 |
Grade A, and why
ha-merge-queue scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Ready-to-Merge Pull Requests
Produce a shortlist of open PRs a maintainer can approve and merge immediately, plus a short list of near-misses that each need one specific nudge. Default to 10 candidates unless the user asks for a different number.
Gather candidates
Search open PRs, excluding those that are structurally not mergeable:
repo:home-assistant/core is:open is:pr draft:false status:success -review:changes_requested
-label:"awaiting-frontend" -label:"stale" -label:"cla-needed"
Add label:"small-pr" for quick wins, or label:"code-owner-approved" / review:approved
for PRs already carrying an approval. Run several searches and pool the results — no single
query surfaces everything.
The search index lags reality by hours. Treat status: as a rough filter, never as proof;
verify every finalist with the per-PR checks below.
Verify each finalist
Check all six conditions. A PR fails the shortlist if any of checks 1 through 5 fail.
Paginate every list response before deciding. Check runs, reviews and review threads are all paged, typically 30 per page, and a full-suite Home Assistant PR runs to 40-odd check runs — so page one shows a green subset while a failure or a standing review sits on page two. Compare the returned count against the reported total and keep fetching until they match.
-
Merge-gate statuses — fetch the combined commit status. This is the cheapest and most informative call, and it is what actually blocks the merge button. Five contexts matter:
code-owner-approval(required for Platinum integrations),required-labels(red when the author checked no "Type of change" box),docs-missing(red when a user-facing change has no documentation PR),cla-bot, andblocking-label-awaiting-frontend. -
Check runs — the commit statuses do not cover GitHub Actions. Fetch the check runs and require every one to have reached an acceptable terminal result:
statusmust becompleted, andconclusionmust besuccess,skippedorneutral. Everything else disqualifies —failure,cancelled,timed_out,action_requiredandstale, and any run stillqueuedorin_progress. A green combined status sitting on top of a red or still-running test job is common, so the status list alone is never enough.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 133 lines · 72 tokens per session scan A 899d68fb9942
ha-merge-queue is a skill published in the GitHub repository home-assistant/core (91,801 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 1,886 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
issue-to-pr-resolver
Implement a GitHub issue end-to-end — create a worktree branch, implement the feature with tests, create a draft PR, then iteratively resolve all CI failures and review comments until the PR is clean. Use when you need to fully implement a GitHub issue from start to merge-ready. Triggers on "implement issue", "resolve…
my-pr-checker
Manage your own GitHub pull requests — check CI status, inline review comments, PR-level comments, resolve review threads, fix issues, and iterate until all checks pass and threads are resolved. Use for managing your own PRs (not external contributions). Triggers on "check my PR", "check PR", "/my-pr-checker ".
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
review-prs
Triage open PRs — screen from the diff, delegate the admission judgment to audit-the-list, then merge or close on GitHub. Fire when the maintainer asks to review PRs, process the PR queue, or judge whether a specific PR should be merged.
stacking-prs
Create and manage GitHub native Stacked PRs in this repo with the gh stack CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers creating and submitting…
reviewing-personhog-protocol
The full review process for personhog coordination-protocol changes — leases, fencing, handoffs, supervisors, failure budgets, warming, and changelog semantics. Use before pushing or requesting review on any personhog protocol changeset, when asked for an exhaustive or careful review of personhog code, and after any…