← ClaudeAtlas

ha-diagnostics-augmentlisted

Enriches an existing Home Assistant Custom Integration's diagnostics beyond the scaffold baseline, conforming to spec/ha/diagnostics. Creates or edits diagnostics.py with async_get_config_entry_diagnostics (and optional async_get_device_diagnostics) returning structured dicts, and routes every secret/PII/credential/coordinate field through async_redact_data with an explicit module-constant TO_REDACT frozenset — never manual truncation or field deletion. Includes redacted coordinator snapshots and version strings in the dump. Pairs with the diagnostics quality-scale rule (Silver). Activate on "enrich diagnostics", "add device diagnostics", "make sure diagnostics redacts secrets", or equivalent German requests. Do not activate to audit redaction gaps across modules (ha-security-audit), to scaffold the bare diagnostics stub at greenfield (ha-integration-scaffold), to score the quality-scale rule (ha-quality-scale-audit), or to deploy to a live HA instance.
nolte/claude-home-assistant · ★ 1 · AI & Automation · score 68
Install: claude install-skill nolte/claude-home-assistant
# HA Diagnostics Augment Spec: `spec/claude/ha-diagnostics-augment/en.md` (EN canonical) / `spec/claude/ha-diagnostics-augment/de.md` (DE translation). ## Why this is a skill, not an agent - **Human-visible augmentation surface** — the user describes the integration and reads back `diagnostics.py`, the `TO_REDACT` set, and the conformance report; a skill keeps this on the visible command surface, like the sibling augment skills (`ha-config-flow-augment`, `ha-coordinator-add`, `ha-repairs-add`, `ha-device-automation-add`). - **Mid-flow interactivity** — the redaction-key classification (which `entry.data` fields are credentials/identifiers/coordinates) is a per-run dialogue the user confirms before generation. - **Bounded, inline generation** — one module plus its `TO_REDACT` set and the dump structure fit inline; no isolated agent context is needed. - Counter-dimension considered: the derive→validate loop could be an agent, but the redaction-key classification belongs in the user's working context; skill wins. ## When this skill activates Use this skill to enrich an existing integration's diagnostics beyond the scaffold baseline — a complete, structured `async_get_config_entry_diagnostics` dump (and optionally `async_get_device_diagnostics`) that routes every sensitive field through `async_redact_data` and includes redacted coordinator snapshots. ## When NOT to activate - auditing redaction gaps across modules (findings report) → `ha-security-audit` - the bare diagnost