// 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.
Create and publish a new GitHub release for this repository, then verify that the related GitHub Actions firmware release build starts. Use when the user says "/release", "make a release", "create a GitHub release", "publish a release", "tag a release", "major release", "feature release", "minor release", "patch release", "start the release action", or wants firmware release assets generated by GitHub Actions.
Compile and flash ESPHome firmware locally to a USB-connected ESP32 device using Docker. Use when the user says "deploy locally", "dploy over usb", "build and flash", "upload firmware", "flash over USB", "test locally", or wants to test component changes on a physical device.
| 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. |
Summarize changes made to this project in the last 7 days, focused on what a user would care about.
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>
Include changes that add or improve something users can notice, such as:
Ignore changes that are mostly internal:
Order the final list by user importance, not by commit date. Prefer this order:
Group related commits into one entry when they describe the same user outcome. Keep only the most meaningful user-facing changes.
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.