k1-firmware-ops

Build selected K1.node2 pattern(s), upload firmware to the ESP32-S3 over LAN, verify the web API/UI, capture artifacts, and draft release notes.

Stars 163

Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/k1-firmware-ops

SKILL.md

K1 Firmware Ops

Purpose

Create a repeatable, end-to-end flow for K1.node2: codegen → compile → OTA → API/UI QA → release notes.

Edit tools/k1.config.json in the repo root to match your setup:

json

{
  "device_ip": "192.168.1.50",
  "ota_method": "arduino",
  "dashboard_path": "/",
  "pattern": "Twilight",
  "upload_port": "3232"
}

Build & Upload (uses existing project scripts and/or PlatformIO):
bash
```
bash tools/k1_firmware_ops.sh --pattern "<PATTERN_NAME>" --ip "<DEVICE_IP>" --qa false
```
- Artifacts land under artifacts/<timestamp>/ (build log and metadata).

Install QA deps once:

bash

cd tools/qa/playwright
npm ci
npx playwright install
cd ../../..

Run API + UI tests (captures JSON report + screenshots):

bash

bash tools/k1_firmware_ops.sh --pattern "<PATTERN_NAME>" --ip "<DEVICE_IP>" --qa true

Generate release notes (Markdown summary with links to artifacts):
bash
```
node tools/release/generate_release_notes.mjs
```

Rebuild and upload Twilight to 192.168.1.50 and run QA:

bash

bash tools/k1_firmware_ops.sh --pattern "Twilight" --ip "192.168.1.50" --qa true

Build only (no QA), using tools/k1.config.json defaults:
bash
```
bash tools/k1_firmware_ops.sh
```

Treat IPs and Wi‑Fi credentials as secrets; do not commit secrets.
Prefer ArduinoOTA unless an HTTP OTA endpoint is documented and reachable.
If /api/params POST semantics differ from the tests, update tools/qa/params.sample.json and the tests accordingly.