Summarize user-facing project changes from the last 7 days. Use when the user says "/updates", asks for recent updates, wants a changelog-style summary, or wants the most important feature changes from the past week.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Summarize what changed in this project over the last 7 days, focusing on user-facing features and behavior rather than implementation details.
Use the current date as the endpoint and inspect commits from the last 7 days.
git status --short --branch
git fetch origin --prune
git log --since="7 days ago" --date=short --pretty=format:'%h %ad %s' --decorate
git log --since="7 days ago" --name-only --pretty=format:'commit %h %ad %s' --date=short
If the local branch is behind or stale, note that the summary is based on the available local history unless a fetch succeeded.
For each meaningful change, inspect enough context to explain what a user can now do, see, configure, or rely on.
Useful commands:
git show --stat <commit>
git show --name-only <commit>
git show -- <path>
Prioritize these as user-facing:
Usually skip these unless they clearly affect users:
Sort the summary by practical user impact:
When importance is close, put broader changes before narrow device- or page-specific changes.
Use one sentence per item in this format:
Feature: description of the user-facing change.
Rules:
Updates from <start date> to <end date>:
- Feature: <one-sentence description>
- Feature: <one-sentence description>
If the 7-day window is ambiguous, use exact dates in the heading.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Clean up completed Git branches and worktrees for this repository both locally and on GitHub. Use when the user asks to remove complete, completed, merged, stale, finished, or done branches, delete merged GitHub branches, tidy local worktrees, prune completed PR branches, or clean up branches and worktrees after pull requests have merged.
The English summary is being prepared. Showing the original description.
Clean up local branch worktree folders for this repository after their branches or pull requests have merged to main. Use when the user asks to remove merged branch folders, tidy local worktrees, clean old feature branch directories, prune merged PR worktrees, or clean up local development folders without impacting main.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Review EspControl repository changes specifically for missing, stale, excessive, or misplaced documentation. Use when the user asks for a documentation coverage review, asks whether a feature or behavior change is concisely documented, invokes $docs-review, or explicitly wants docs checked as a secondary pass during a pull request, branch, or local diff review.
The English summary is being prepared. Showing the original description.
Provide an expert codebase review for this repository. Use when the user says "Expert Review" or "/expert-review", asks for an expert review, wants refactoring or codebase improvement recommendations, wants consistency and quality assessed, or asks how to reduce duplication, improve component use, preserve the end-user experience, and keep upgrades cleanly migratable.
The English summary is being prepared. Showing the original description.
Reimagine this repository from first principles using the current product and user experience as the target. Use when the user says "/expert-reset", asks how the project should be rebuilt if starting again, wants bold architecture or component-structure recommendations, or wants a research-only reset plan unconstrained by current implementation details.
The English summary is being prepared. Showing the original description.