claude

home-assistant-dev

Comprehensive Home Assistant integration development toolkit with 27 skills, MCP server for live HA connection, automated validation, example integrations, and project templates

8 on GitHubby L3DigitalNetv2.2.11MITupdated 2 months ago
/

Plugin home-assistant-dev from marketplace l3digitalnet-plugins in L3DigitalNet/Claude-Code-Plugins. Commands read from the repo's manifest — 1 month ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use and it starts local MCP servers. The exact commands are listed below; read them before installing.

What it installs

Skills (27)

  • ha-architecture

    Home Assistant core internals — event bus, state machine, service registry, and integration loading. Use when asking about the hass object, event propagation, state management, service registration, or how integrations load.

  • ha-async-patterns

    Write correct async Python code for Home Assistant integrations. Use when mentioning async, await, event loop, blocking, executor, async_add_executor_job, coroutine, or asking about performance and non-blocking code in Home Assistant.

  • ha-blueprints

    Home Assistant YAML blueprints — reusable automation templates with configurable inputs. Use when building a blueprint, defining blueprint inputs, or creating a shareable automation template.

  • ha-config-flow

    Home Assistant config flow for initial integration setup. Use when creating or debugging config_flow.py, the user-facing setup wizard, unique_id handling, or strings.json for the setup steps.

  • ha-config-migration

    Config entry version migration in Home Assistant. Use when incrementing VERSION or MINOR_VERSION, implementing async_migrate_entry, or migrating stored entry data between schema versions.

  • ha-coordinator

    Implement or fix a Home Assistant DataUpdateCoordinator for centralized data fetching. Use when mentioning coordinator, DataUpdateCoordinator, polling, data fetching, _async_update_data, _async_setup, UpdateFailed, or setting up efficient data polling for a Home Assistant integration.

  • ha-debugging

    Debug and troubleshoot Home Assistant integration issues. Use when mentioning error, debug, not working, unavailable, traceback, exception, logs, failing, ConfigEntryNotReady, UpdateFailed, or needing help diagnosing HA integration problems.

  • ha-deprecation-fixes

    Fix Home Assistant deprecation warnings and upgrade integrations to newer HA versions. Use when encountering deprecated imports, type annotations, or patterns that need updating for HA 2024.x/2025.x compatibility.

  • ha-device-conditions-actions

    Device conditions and actions for Home Assistant automation. Use when implementing device_condition.py, device_action.py, condition state checks, or device-level automation actions.

  • ha-device-triggers

    Device triggers for Home Assistant automation. Use when implementing device_trigger.py, allowing automations to fire on hardware events like button presses or motion detection.

  • ha-diagnostics

    Implement diagnostics for a Home Assistant integration. Required for Gold tier on the Integration Quality Scale. Use when asked about diagnostics.py, debug information, troubleshooting data, or redacting sensitive info.

  • ha-documentation

    Generate documentation for Home Assistant integrations. Creates README.md, Home Assistant docs pages, and HACS info pages. Use when asked about documentation, README, docs, or making documentation for an integration.

  • ha-entity-lifecycle

    Entity lifecycle and device/entity registries in Home Assistant. Use when asking about entity registration, async_added_to_hass, async_will_remove_from_hass, device_info, identifiers, or restoring previous state.

  • ha-entity-platforms

    Create Home Assistant entity platforms (sensor, binary_sensor, switch, light, cover, climate, button, number, select, etc.). Use when creating entities, adding platforms, implementing switches or sensors, or working with any HA entity type.

  • ha-hacs-publishing

    Publish a Home Assistant integration to HACS — GitHub Actions validation, release workflow, brand submission, and adding to the HACS default repository.

  • ha-hacs

    HACS metadata requirements for a Home Assistant integration — hacs.json, manifest.json fields, and repository structure. Use when preparing or validating HACS metadata files.

  • ha-integration-scaffold

    Scaffold a new Home Assistant integration with correct file structure, manifest, and boilerplate. Use when creating a new custom component, custom integration, or when asked to scaffold, create, or start a Home Assistant integration.

  • ha-migration

    Home Assistant integration upgrade guide — config entry version migration and deprecation fixes. Use when upgrading an integration to a newer HA version or handling migration warnings.

  • ha-options-flow

    Home Assistant options flow for post-setup user preferences. Use when adding or fixing an options flow, allowing users to change integration settings after initial setup, or implementing reauth when credentials expire.

  • ha-quality-review

    Review a Home Assistant integration against the Integration Quality Scale (IQS). Covers all 52 official rules across Bronze, Silver, Gold, and Platinum tiers. Use when asked to review, quality check, assess for core PR, HACS submission, or IQS compliance.

  • ha-recorder

    Work with the Home Assistant recorder and statistics. Use when asked about history, statistics, long-term stats, database, recorder exclusion, or historical data.

  • ha-repairs

    Implement repair issues for Home Assistant integrations. Gold tier IQS requirement. Use when asked about repair issues, issue registry, user notifications, fixable issues, or actionable alerts.

  • ha-scripts

    Home Assistant YAML scripts — callable, reusable action sequences with optional parameters. Use when creating a script, defining a reusable sequence, or adding parameterized fields to a script.

  • ha-service-actions

    Generate and explain Home Assistant service actions for controlling entities (lights, switches, climate, media, covers) in Python and YAML. Use when asking about calling services, controlling devices, hass.services.async_call, entity actions, turn_on, turn_off, or invoking HA actions.

  • ha-testing

    Write tests for Home Assistant integrations using pytest and the hass fixture. Use when mentioning test, pytest, testing, test coverage, mock, fixture, or preparing an integration for core submission.

  • ha-websocket-api

    Implement WebSocket API commands for Home Assistant integrations. Use when asked about WebSocket API, custom API endpoints, frontend integration, custom panels, or real-time data to frontend.

  • ha-yaml-automations

    Home Assistant YAML automations — triggers, conditions, and actions. Use when writing or fixing an automation, choosing a trigger type, or structuring automation logic.

Slash commands (2)

  • /home-assistant-dev:generate-integration

    Generate a complete Home Assistant integration from scratch with all necessary files. Interactive command that scaffolds a full integration based on user requirements.

  • /home-assistant-dev:scaffold-integration

    Scaffold a new Home Assistant integration with all required files

Subagents (3)

  • ha-integration-debugger

    Home Assistant integration debugger. Use PROACTIVELY when encountering errors, test failures, or unexpected behavior in HA integrations.

  • ha-integration-dev

    Home Assistant integration development specialist. Use PROACTIVELY when creating, reviewing, or debugging Home Assistant integrations. Expert in DataUpdateCoordinator patterns, config flows, entity platforms, and the Integration Quality Scale.

  • ha-integration-reviewer

    Home Assistant integration code reviewer that scores integrations against the Integration Quality Scale (Bronze/Silver/Gold). Use this agent when reviewing or grading integration code. Typical triggers include after writing or modifying config_flow.py, before preparing a HACS or core submission, aft

MCP servers (1)

  • ha-dev-mcp

    runs: node ${CLAUDE_PLUGIN_ROOT}/mcp-server/dist/server.bundle.cjs

Hooks (1)

  • PostToolUse

    bash ${CLAUDE_PLUGIN_ROOT}/scripts/post-write-hook.sh

View source on GitHub

More from L3DigitalNet/Claude-Code-Plugins

All 6 plugins →

qt-suite

claude

Qt development and testing toolkit: proactive specialist agents, 16 domain references, scaffolding commands, and headless GUI testing via Qt Pilot MCP for PySide6, PyQt6, and C++/Qt projects.

6 commands · 6 agents · 1 MCP server

8

up-docs

claude

Update documentation across three layers (repo, llm-wiki, Notion) via sub-agent propagation plus drift audit, all on Sonnet. Five commands for targeted updates and comprehensive drift analysis with four-phase convergence.

5 skills · 4 agents · hooks

8

Spec-driven autonomous development pipeline: author a master spec, decompose into phases, execute each phase under TDD with deterministic specpipe validator gates (structure, dependency graphs, decision-id citations, TDD step order, RED/GREEN evidence, round caps) in front of every review pass.

2 skills · 3 commands

8

Python Tooling SSOT Standard: uv + Ruff + BasedPyright (strict) + pytest/coverage + pip-audit. Operationalizes a single, strict, boring toolchain that behaves identically in CLI, VS Code, and CI. Use when creating Python projects, migrating to uv, auditing conformance, or replacing legacy tooling.

1 skill · hooks · LSP

8

qdev

claude

Deep web research for development decisions: /research dispatches a Sonnet subagent for a dual-source sweep (Tavily-first recall, Brave/Serper cross-checks, Context7 docs gating, footgun corroboration) and persists a structured, frontmatter-indexed report under docs/research/. User-initiated only.

1 command · 1 agent

8

Maintain home-assistant-dev?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins6 plugins