Menu
Guidance for Home Assistant configurations. Use when writing automations, dashboards, or service calls for HA.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Traces code history via git blame and log to explain why code exists in its current form. Use when asked about code history, reasoning behind changes, or "when/why did this change".
Commit changes with smart messages. Supports full and partial commits. Use whenever committing changes or handling pre-commit hook failures.
Use the gh CLI for GitHub interactions, plus setup and pushing. Use when interacting with GitHub, setting up GitHub tools, or pushing to remote.
Universal polyglot linting and per-project config management. Use when you need to lint files, understand tool selection logic, invoke linting from commands/agents, or manage mr-sparkle config.
Resolves git merge conflicts by analyzing intent from both sides. Use when merge conflicts are detected or when git operations fail with conflict errors.
Create a pull request with Problem/Solution format. Can optionally commit first. Use when opening PRs or when branch changes are ready for review.
| name | home-assistant |
| description | Guidance for Home Assistant configurations. Use when writing automations, dashboards, or service calls for HA. |
Fetch official docs for current syntax - HA evolves rapidly:
target: + data:, not entity_id: at rootid and explicit mode!secret, never hardcodedClaude may generate deprecated patterns. Use modern syntax:
# Wrong: deprecated
service: homeassistant.turn_on
entity_id: light.porch
# Right: modern
service: light.turn_on
target:
entity_id: light.porch
Automations need id and mode:
automation:
- id: porch_light_sunset
alias: "Porch light at sunset"
mode: single # or restart, queued, parallel
trigger:
- platform: sun
event: sunset
action:
- service: light.turn_on
target:
entity_id: light.porch
Unreliable devices need guards:
action:
- choose:
- conditions:
- condition: template
value_template: >
{{ states('light.unreliable_bulb') not in ['unavailable', 'unknown'] }}
sequence:
- service: light.turn_on
target:
entity_id: light.unreliable_bulb
State triggers fire on every change. Use thresholds or debounce:
# Threshold: only fires when crossing
trigger:
- platform: numeric_state
entity_id: sensor.temperature
above: 75
# Debounce: must stay in state
trigger:
- platform: state
entity_id: sensor.temperature
for:
minutes: 5
Use templates for dynamic content:
# Bad
message: "Front door opened"
# Good
message: "Front door opened at {{ now().strftime('%I:%M %p') }}"