ha-device-registry-augmentlisted

Wires the device-registry hierarchy of an existing Home Assistant Custom Integration so entities group into proper devices — DeviceInfo with identifiers / manufacturer / model / name, a via_device hub-to-child parent link, runtime addition of newly discovered devices, and removal of stale devices via async_remove_config_entry_device. Optionally adds async_get_device_diagnostics. Targets the Gold devices, stale-devices, dynamic-devices rules. Non-destructive to existing entities. Activate on phrasings like "group these entities into a device", "add a hub device with child devices via_device", "remove stale devices when they disappear", "gruppiere die Entitäten zu einem Gerät", "füge ein Hub-Gerät mit Kindgeräten hinzu". Do not activate for creating entity platforms (ha-entity-platform-add), config-entry diagnostics (ha-diagnostics-augment), device trigger/condition/action automations (ha-device-automation-add), greenfield scaffolding (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 Device Registry Augment Spec: `spec/claude/ha-device-registry-augment/en.md` (EN canonical) / `spec/claude/ha-device-registry-augment/de.md` (DE translation). This skill owns the **device-registry hierarchy** — `DeviceInfo`, `via_device`, dynamic device add, and stale device removal — that `ha/entity-architecture` describes but no skill wires. It lifts an integration from flat entities toward the Gold `devices` / `stale-devices` / `dynamic-devices` rules. ## Why this is a skill, not an agent - **Human-visible augmentation surface** — the user describes the device topology and reads back the `DeviceInfo` wiring, the `via_device` link, and the removal path; a skill keeps this on the visible command surface, like the sibling augment skills. - **Mid-flow interactivity** — the device topology (one device, a hub with children, per-datapoint devices), the identifier source, and whether stale-device removal applies are per-run dialogues the user confirms. - **Bounded, inline generation** — the `DeviceInfo` construction plus the removal hook fits inline; no isolated agent context is needed. - Counter-dimension considered: the draft→validate loop could be an agent, but the topology decision and the report belong in the user's working context; skill wins. ## When this skill activates Use this skill when an existing integration's entities should group into one or more **devices** — a single device, a hub with `via_device` children, or per-physical-device grouping — and when de