updates

name	updates
description	Summarize user-facing project updates from the last 7 days, ordered by importance and written as one-sentence "Feature: description" entries. Use when the user says "/updates", asks what changed recently, or wants a concise list of recent features, device support, fixes that users will notice, or other product value.

Recent User-Facing Updates

Summarize changes made to this project in the last 7 days, focused on what a user would care about.

Workflow

1. Gather Recent Changes

Use git history from the last 7 days, including commit messages and changed files:

git log --since="7 days ago" --date=short --pretty=format:'%h %ad %s'
git log --since="7 days ago" --name-status --date=short --pretty=format:'%h %ad %s'

If the local branch may be stale, fetch first:

git fetch origin --prune

When commit messages are too vague, inspect the relevant diffs:

git show --stat <commit>
git show <commit> -- <path>

2. Filter For User Value

Include changes that add or improve something users can notice, such as:

• New device support or hardware variants
• New features or visible behavior changes
• Setup, install, update, dashboard, documentation, or release improvements
• Bug fixes with clear user impact
• Firmware, display, audio, touch, Wi-Fi, Bluetooth, or Home Assistant behavior that changes the user experience

Ignore changes that are mostly internal:

• Refactoring, cleanup, renames, formatting, dependency chores, or build plumbing
• Minor code tweaks without clear user impact
• Test-only changes unless they explain a shipped behavior fix
• CI-only changes unless they directly affect release availability for users

3. Prioritize The Results

Order the final list by user importance, not by commit date. Prefer this order:

1. New or expanded device support
2. New user-facing features or visible behavior changes
3. Fixes for problems users could encounter
4. Setup, installation, update, release, or documentation improvements

Group related commits into one entry when they describe the same user outcome. Keep only the most meaningful user-facing changes.

4. Write The Summary

Be concise. Return a short list in this format:

Feature: One plain-language sentence explaining what changed for users.

Each entry must be a single sentence. Prefer 3-6 entries, and use fewer if there were only a few meaningful user-facing updates. Do not include commit hashes unless the user asks for them.

If there were no meaningful user-facing updates in the last 7 days, say that plainly and mention that you ignored internal maintenance changes.