// Summarize user-facing changes made to this project over the last 7 days. Use when the user says "/updates", asks for recent updates, weekly updates, release-style highlights, or wants a concise feature summary ordered by importance.
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.
Test compile ESPHome firmware for all devices using Docker and fix any YAML or configuration errors until every device compiles successfully. Use when the user says "/compile", "test compile", "compile check", "build test", "check builds", "verify compile", or wants to make sure all devices compile before committing.
| name | updates |
| description | Summarize user-facing changes made to this project over the last 7 days. Use when the user says "/updates", asks for recent updates, weekly updates, release-style highlights, or wants a concise feature summary ordered by importance. |
Summarize the project's user-facing changes from the last 7 days in plain language. Focus on what a user can see, configure, install, fix, or benefit from, not internal implementation details.
Check the current branch and update remote refs without changing branches:
git status --short --branch
git fetch origin --prune
Review commits from the last 7 days:
git log --since="7 days ago" --date=short --pretty=format:"%h %ad %s%n%b"
Inspect changed files when commit subjects are not enough:
git log --since="7 days ago" --name-status --oneline
git diff --stat "HEAD@{7 days ago}" HEAD
If reflog history is unavailable, use the commit list from step 2 and inspect
individual commits with git show --stat <sha> or git show <sha>.
Group related commits into user-facing items. Prefer these categories:
Order items by importance:
Use one sentence per item in this exact style:
Feature: description of feature.
Keep the wording approachable for a technical but non-development-oriented reader. Avoid commit hashes, file names, PR numbers, and implementation jargon unless the user asks for them.
If there are no clear user-facing changes, say that directly in one sentence and briefly mention that the recent work appears to be internal maintenance.