l3digitalnet/ha-migration
plugins/home-assistant-dev/skills/ha-migration/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add l3digitalnet/claude-code-plugins ha-migrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 6:02 PM126.4s1 file scanned
SKILL.md
- 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.
Home Assistant Integration Migration
This skill is an entry point for two distinct migration concerns:
Config Entry Version Migration
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.
Deprecation Fixes
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.
Migration Checklist (Per Version Upgrade)
- Check the Home Assistant Developer Blog for breaking changes
- Search for deprecated imports in your code
- Run
check-patterns.pyto detect common issues:python3 scripts/check-patterns.py custom_components/my_integration/ - Update minimum HA version in
hacs.json - Test against target HA version
Related Skills
- Config entry migration →
ha-config-migration - Deprecation patterns →
ha-deprecation-fixes - Integration structure →
ha-integration-scaffold
Related Skills
l3digitalnet/qdev-grounding
development
VerifiedTrustedCommunity
Use when you're stuck or missing current information mid-task - the same command/API/approach failed twice, an error looks like a changed or deprecated API, or you need the current version of something, a fact from after your training cutoff, or to verify something you cannot confirm from the code in context. Starts with a cheap inline lookup and only escalates to a full research sweep if that fails. Do not use for routine pre-emptive checks before ordinary library work - for deliberate research, use /qdev:research.
5SKILL.mdUpdated Jun 4, 2026
l3digitalnet/up-wiki
documentation
VerifiedTrustedCommunity
Update Outline wiki documentation with implementation-level details from the current session by dispatching the up-docs-propagate-wiki sub-agent. This skill should be used when the user runs /up-docs:wiki.
5SKILL.mdUpdated Apr 24, 2026
l3digitalnet/up-repo
documentation
VerifiedTrustedCommunity
Update repository documentation (README.md, docs/, CLAUDE.md) based on session changes by dispatching the up-docs-propagate-repo sub-agent. This skill should be used when the user runs /up-docs:repo.
5SKILL.mdUpdated Apr 24, 2026
l3digitalnet/up-notion
documentation
VerifiedTrustedCommunity
Update Notion pages with strategic and organizational context from the current session by dispatching the up-docs-propagate-notion sub-agent. This skill should be used when the user runs /up-docs:notion.
5SKILL.mdUpdated Apr 24, 2026