Create a reviewable post asking people to test an EspControl feature branch. It can include a copyable ESPHome configuration, steps tied to the feature being checked, and details testers should report, such as their display model and any errors.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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.아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Preview completed Git branches and worktrees that are safe to remove, then clean them up locally. With an additional option, delete matching remote branches on GitHub. The workflow skips protected branches, open pull requests, and worktrees with uncommitted changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Find local Git worktree folders whose branches or pull requests have merged into main, then preview which clean, inactive folders can be removed. The bundled script defaults to a dry run and requires an explicit apply option to perform cleanup.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Compile ESPHome firmware for every listed device using the version pinned by the repository and Docker. When a build fails, inspect the reported YAML or configuration issue, fix its source, and retry until each device compiles.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Check a code change for missing, outdated, excessive, or misplaced documentation. Identify only actionable gaps, explain who needs the information, and suggest the smallest useful update and a suitable existing documentation location.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review a codebase and receive ranked recommendations for maintainability, consistency, reuse, quality, and safer upgrades. Findings are explained in plain language with evidence, user impact, migration approaches, risk controls, and estimated effort; the review does not make changes by default.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review a project as if rebuilding it today while keeping its current user experience as the target. Produce evidence-based architecture and migration recommendations, explain tradeoffs in plain language, and keep the work research-only unless implementation is requested separately.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.