← ClaudeAtlas

ha-integration-upgradelisted

Use when moving a Home Assistant custom integration to a newer core release (for example 2026.10 to 2026.11), bumping its homeassistant or pytest-homeassistant pin, raising the hacs.json minimum, or asking which breaking changes, deprecations, or new core helpers of a Home Assistant release affect a custom component.
pszypowicz/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill pszypowicz/claude-skills
# Upgrading a Home Assistant custom integration ## Overview Every monthly core release can break a custom integration, deprecate what it calls, and add helpers that make some of its own code redundant. This skill turns one release step into a report with evidence for each finding, and then, once the user approves, into themed PRs with the repo's own gate green. Discovery runs against live sources every time, and the skill carries no list of helpers. The core source at the release tag is the authority. Blog posts, PR titles and labels only nominate candidates. The integration's own gate, run on the new pin, is the fastest detector of what breaks. ## Inputs - **The step.** The release the repo pins now and the one it moves to. Read the current pin from the repo (the test requirements, the `homeassistant` key of `hacs.json`, the CI matrix) and say so when it differs from what the user named. When the pin is more than one minor behind the target, process one minor at a time: 2026.9 to 2026.10, then 2026.10 to 2026.11. Each step gets its own report section, and a finding carries the release that introduced it. - **The repo's policy.** Read `AGENTS.md`, `CLAUDE.md`, `CONTRIBUTING.md` and the gate configuration (`.pre-commit-config.yaml`, CI workflows, `pyproject.toml`). Note what they say about migration and compatibility code, how far the minimum Home Assistant version may move, the type checkers, test conventions such as snapshots, the branch and PR rules