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.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Post a short, friendly GitHub issue comment saying the change will be included in the next release and asking the reporter to leave feedback after testing.
Identify the GitHub issue from the current chat context.
Confirm the target issue is in this repository unless the chat clearly points somewhere else.
Post this comment, adjusting only the greeting if the reporter's name is obvious:
Thanks for reporting this. The fix has been merged and will be included in the
next release.
Once you have a chance to try that release, please leave feedback here and let
us know whether it resolves the issue for you.
Do not close the issue. The project owner wants to test or receive feedback before issues are closed.
After posting, reply with the issue number and a short confirmation. If the platform returns a comment URL, include it.
Prefer the GitHub app/connector when available. If not, use the GitHub CLI from the repository checkout, for example:
gh issue comment <issue-number-or-url> --body-file <temporary-body-file>
Use a temporary file for the comment body to avoid shell quoting mistakes.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。