القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when starting or closing an agent session, routing durable repository facts, maintaining status or task state, recording bugs, validating handoff conformance, or reconciling an older handoff layout.
Configures Python projects to the Python Tooling SSOT Standard (uv, Ruff, BasedPyright strict, pytest+coverage, pip-audit). Use when creating projects, writing standalone scripts, configuring pyproject.toml, migrating from pip/Poetry/mypy/black/flake8, or auditing a project for conformance to the standard.
Author the canonical project spec and decompose it into phases for execution by /spec-pipeline:execute-phase. Run once at project inception.
Execute the next pending phase of the named project end-to-end — derive the phase spec from the master, plan it, implement under TDD with review gates, and update handoff state. Run once per phase, passing the project name.
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.
HACS metadata requirements for a Home Assistant integration — hacs.json, manifest.json fields, and repository structure. Use when preparing or validating HACS metadata files.
| name | ha-migration |
| description | 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. |
This skill is an entry point for two distinct migration concerns:
When your config entry schema changes (renaming keys, adding required fields), you need to increment VERSION and implement async_migrate_entry.
See ha-config-migration for the full pattern and template.
When to use it: You changed what's stored in entry.data or entry.options and existing users' data needs to be transformed.
When upgrading to a newer HA version, imports, type annotations, and API patterns that were deprecated may now emit warnings or fail.
See ha-deprecation-fixes for 2024–2025 deprecation patterns with before/after examples.
When to use it: You see deprecation warnings in HA logs, or you're upgrading homeassistant minimum version in hacs.json.
Check the Home Assistant Developer Blog for breaking changes
Search for deprecated imports in your code
Run check-patterns.py to detect common issues:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/check-patterns.py" custom_components/my_integration/
Update minimum HA version in hacs.json
Test against target HA version
ha-config-migrationha-deprecation-fixesha-integration-scaffold