ha-hacs-releaselisted

Makes an existing Home Assistant Custom Integration HACS-release-ready by scaffolding and verifying the HACS-specific distribution layer defined in spec/ha/hacs-release — a valid hacs.json (name, zip_release plus filename, homeassistant floor, hide_default_branch, render_readme), the manifest.json version aligned to the vMAJOR.MINOR.PATCH release-tag scheme, the ZIP-release CD obligation (build and attach the domain.zip asset), and the brands registration pointer. Operationalizes the HACS layer on top of the generic release flow (spec/project/release-automation) without redefining it. Activate on "make this integration HACS-release-ready", "add a hacs.json", "set up ZIP release for HACS", or equivalent German requests. Do not activate for the generic release publish flow itself (nolte-shared:release-publish-trigger), the CI validation workflow (ha-integration-ci-scaffold), the integration code (ha-integration-scaffold), or deploying to a live HA instance.
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

Install: claude install-skill nolte/claude-home-assistant

# HA HACS Release Spec: `spec/claude/ha-hacs-release/en.md` (EN canonical) / `spec/claude/ha-hacs-release/de.md` (DE translation). This skill operationalizes `spec/ha/hacs-release/en.md` — the HACS-specific distribution layer (`hacs.json`, version alignment, ZIP release, `brands`) — on top of the portfolio's generic `release-automation` flow. It closes the audit finding that the `ha/hacs-release` spec exists but no skill or agent makes a consumer integration HACS-release-ready. ## Why this is a skill, not an agent - **Human-visible augmentation surface** — the user reads back `hacs.json`, the version-alignment check, and the ZIP-CD wiring and confirms the distribution model; a skill keeps this on the visible command surface. - **Mid-flow interactivity** — the ZIP-vs-default-branch distribution choice, the minimum HA version, and whether `brands` is already registered are per-run dialogues the user confirms. - **Orchestrator-leaning** — it surfaces the generic `release-automation` prerequisites and points at `nolte/gh-plumbing` reusable workflows rather than duplicating release logic; the skill-orchestrates default keeps it in skill form. - Counter-dimension considered: the verify loop could be an agent, but the distribution-model decision and the report belong in the user's working context; skill wins. ## When this skill activates Use this skill to make an existing integration installable and updatable through HACS — scaffold or verify `hacs.json`, the manifest/tag vers