メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create and safely publish a new GitHub release for this repository through a verified draft build, then confirm the related GitHub Actions run. 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.
Flash EspControl display firmware from this repository using ESPHome. Use when the user invokes /flash-displays with no extra display name, or asks to flash, reflash, update, or upload firmware to all known displays in sequence, or to a specific display such as 7inch, 7-inch P4, 10inch, 10-inch V1, 10-inch V2, P4-86, 4.3-inch P4, 4-inch P4, or 4-inch S3, over an explicitly supplied OTA target or USB.
Address GitHub pull request feedback for this repository. Use when the user says "/pr-review" and wants review comments, requested changes, or unresolved feedback on an open PR inspected, incorporated into the branch, pushed, and marked resolved after the fix is made.
Research-only technical debt scan for this EspControl repository. Use when the user asks for a tech debt scan, cleanup backlog, maintainability review, messy or rushed implementation review, duplicated logic audit, fragile assumption scan, dead code review, architecture cleanup plan, or asks to identify code that works now but will be painful to maintain later.
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.
| 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.