Draft user-reviewable testing posts for EspControl feature branches, especially manual ESPHome installation instructions and focused hardware feedback steps. Use when the user asks for a feedback request, tester announcement, or review draft for a branch.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Create a complete draft that the user can review before it is posted. Do not publish, comment, or send the draft unless the user separately asks for that action.
Identify the feature branch, pull request, affected display, and the exact user-visible behavior being tested. Inspect repository device documentation or configuration when the device path is not explicit.
Use the branch ref in all GitHub ESPHome package sources that need to provide the feature. A package URL alone normally resolves the default branch; include ref: <branch> when testing an unmerged branch.
For EspControl manual ESPHome installs, include the branch component substitution when the nested device package uses espcontrol_component_ref, for example:
substitutions:
espcontrol_component_ref: "<branch>"
If the feature changes the web UI, point web_server.js_url at the matching branch web asset when practical. Prefer the repository’s established jsDelivr pattern:
web_server:
js_url: https://cdn.jsdelivr.net/gh/jtenniswood/espcontrol@<branch>/docs/public/webserver/embedded/www.js?device=<device-slug>&v=<test-label>
Include a complete, copyable ESPHome YAML example. Use the device’s documented packages.yaml path and matching device slug; do not invent paths. Include Wi-Fi placeholders using the repository’s normal !secret convention unless the user requests inline credentials.
Give testers a short numbered checklist tied to the feature’s acceptance criteria. For climate controls, cover capability visibility, the old control’s behavior, the new control’s behavior, independent backend attributes/services, labels, and unsupported-entity behavior when relevant.
Ask testers to report the display model, ESPHome version, entity or device details, available modes, observed behavior, and any errors. Keep the language friendly and concrete.
esphome run ... section when the user asks for an ESPHome Device Builder/manual-install post without command-line instructions.まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。