ha-esphome-ci-scaffoldlisted

Scaffolds the CI that validates an ESPHome fleet per spec/ha/esphome-project-structure §Validation — a pull-request workflow running esphome config for every device file on every change rather than only the diff, because a package edit breaks devices nobody touched, plus a scheduled or pre-release job for the far slower esphome compile, the static checks alongside them, a pinned ESPHome version, and the environment-variable strategy that lets a validation run resolve credentials without a secret ever being real. Emits workflows following the inherited GitHub-Actions rules: digest-pinned actions, least-privilege permissions, concurrency groups, no untrusted input in a run block. Activate on "add CI for my ESPHome repo", "validate all device configs in CI", or equivalent German requests. Do not activate to lay out the repository (ha-esphome-fleet-scaffold), to fix a red run (workflow-health-triage), to author CI for a custom integration (ha-integration-ci-scaffold), or to compile and flash locally.
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68

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

# HA ESPHome CI Scaffold Spec: `spec/claude/ha-esphome-ci-scaffold/en.md` (EN canonical) / `spec/claude/ha-esphome-ci-scaffold/de.md` (DE translation). Grounding spec: `spec/ha/esphome-project-structure/en.md` §Validation. Workflow mechanics follow the inherited `spec/project/github-actions-best-practices/` and `spec/project/continuous-integration/`. Scaffolds the validation pipeline of an ESPHome fleet — the one gate that catches the failure mode a shared-package repository is built to produce. ## Why this is a skill, not an agent - **Mid-flow approval is the contract (decisive):** the credential strategy for a validation run, the compile cadence, and the ESPHome version floor are operator decisions with cost and security consequences. - **Quick, targeted change in the current context:** one or two workflow files in the repository the conversation is scoped to. - **Counter-dimension considered:** enumerating the fleet and the existing pipeline is self-contained (agent bias), but the resulting workflow is iterated with the operator; the read-only audit of an existing pipeline is a different job and belongs to `cicd-pipeline-reviewer` (nolte-shared) / `ha-esphome-fleet-reviewer`. ## When this skill activates The user wants an ESPHome repository validated automatically — "ESPHome-Configs in CI prüfen", "add a GitHub Actions workflow for my device configs", "how do I catch a broken package before it reaches a device". ## When NOT to activate - the repository tree and the