ha-integration-ci-scaffoldlisted

Scaffolds the Home-Assistant-specific CI validation for a Custom Integration repository — a GitHub Actions workflow running hassfest and the HACS validation action on push and pull_request, plus a pytest job using pytest-homeassistant-custom-component across a Python matrix. Complements the portfolio's generic lint/release CI rather than replacing it; adds only the HA-domain validators. Grounded in spec/ha/dev-workflow (hassfest) and spec/ha/hacs-release (HACS validation gate). Activate on "add hassfest and HACS validation to CI", "set up the integration CI workflow", "add a pytest matrix job for the integration", or equivalent German requests. Do not activate for the generic repo scaffold (nolte-shared:project-structure-apply), the release publish flow (spec/project/release-automation and ha-hacs-release), the Python code itself (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 Integration CI Scaffold Spec: `spec/claude/ha-integration-ci-scaffold/en.md` (EN canonical) / `spec/claude/ha-integration-ci-scaffold/de.md` (DE translation). This skill scaffolds the **HA-domain CI validators** — hassfest, the HACS validation action, and the pytest matrix — that the generic portfolio CI (`nolte-shared:project-structure-apply`, `quality-gate`, `release-automation`) does not emit. It closes the audit finding that `ha-integration-scaffold` claims hassfest CI is "handled by the project-structure scaffold" when in fact nothing HA-specific is generated. The generated YAML targets the **consumer integration repository**, not this plugin repo. ## Why this is a skill, not an agent - **Human-visible augmentation surface** — the user reads back the generated `validate.yml` and the pytest matrix and confirms the Python-version set; a skill keeps this on the visible command surface, like the sibling scaffolders. - **Mid-flow interactivity** — the Python-version matrix, whether the repo is HACS-distributed (so the HACS action applies), and the ZIP-mode toggle are per-run dialogues the user confirms. - **Bounded, inline generation** — one or two workflow files fit inline; no isolated agent context is needed. - Counter-dimension considered: the draft loop could be an agent, but the matrix and delimitation decisions belong in the user's working context; skill wins. ## When this skill activates Use this skill to add the HA-specific CI validation to a Custom Integra