// 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.
| name | updates |
| description | 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. |
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.
Post a standard update comment to a GitHub issue that is already in the chat context. Use when the user says "/post-update", asks to update an issue after a fix has landed, or wants issue participants told that the fix will be in the next release and invited to leave feedback once they can test it.
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.
Provide an expert codebase review for this repository. Use when the user says "/expertreview", 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.
Alias for the repository pull request review workflow. Use when the user says "/pr-review" or asks to review a newly submitted or open GitHub pull request, document what changed, evaluate code quality, security and integration risk, run the relevant local checks, and recommend whether to merge, request improvements, or hold.
Review a new or open pull request for this repository with an adversarial security and quality lens. Use when the user says "/pr", "/pr-review", "check the new PR", "is this PR safe to merge", "look for malicious code", "review outside contribution", "should I merge this PR", or asks for reasons not to merge a pull request.