菜单
Run the tibber-pulse-bot verification protocol — gofmt, go vet, go test, then guide the end-to-end bridge/MQTT smoke tests and the Helm render. Use before reporting a bridge / SML / output change as done.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | verify |
| description | Run the tibber-pulse-bot verification protocol — gofmt, go vet, go test, then guide the end-to-end bridge/MQTT smoke tests and the Helm render. Use before reporting a bridge / SML / output change as done. |
| disable-model-invocation | true |
Runs the project's Verification protocol (see CLAUDE.md › "Verification protocol"). The static gates are CI-gated and run automatically; the end-to-end steps need a real bridge + broker and are run on request.
test -z "$(gofmt -l .)" && echo "gofmt: clean" || { echo "gofmt: FAIL"; gofmt -l .; }
go vet ./...
go test ./...
These three are required checks on main. Stop and fix before going further if
any fail.
helm lint plus a template render of at least one password mode:
helm lint chart
helm template r chart \
--set pulse.host=192.0.2.10 \
--set mqtt.host=mosquitto.default.svc.cluster.local \
--set pulse.password=dummy-9char
Expect zero errors. For the other two password modes swap the last --set for
--set pulse.sealedSecret.encryptedPassword=... or --set pulse.existingSecret=....
These need the real bridge IP and the 9-char sticker password — never commit
them. Ask the operator for <ip> and <pw>, or read $TIBBER_PULSE_PASSWORD.
a. Stdout smoke test — expect ≥ 5 readings per frame, including meter_serial:
go build -o tibber-pulse-bot ./cmd/tibber-pulse-bot
./tibber-pulse-bot --pulse-host <ip> --pulse-password <pw>
b. MQTT round-trip — run the bot against the broker in one shell, subscribe
in another, and confirm power_total updates every ~2–4 s:
./tibber-pulse-bot --pulse-host <ip> --pulse-password <pw> --mqtt-host <broker>
# separate shell:
mosquitto_sub -h <broker> -t 'tibber/pulse/#' -v
State which steps ran and their results. Do not claim "verified" if the end-to-end steps were skipped — say so explicitly.
Audit tibber-pulse-bot for internal inconsistencies and documentation drift — CLI flags vs docs, image version/digest sync across chart/compose/README, module-path consistency, CLAUDE.md path references, env-var and chart-values parity, and code defaults vs documented defaults. Use before a PR merge (the pre-merge review gate expects it) or whenever you want to confirm docs still match the code. Read-only: reports drift, never edits.
Ship a new tibber-pulse-bot release. Releases are automatic — release.yml patch-bumps and tags on every code merge to main. Use this to drive and verify that pipeline, or to cut a manual minor/major tag when a patch bump isn't enough.