board-debug-assistant

name	board-debug-assistant
description	Guide and perform interactive embedded-board debugging through the local Board Debug Assistant serial session. Use when the user asks Claude Code or Codex to inspect a connected board, monitor boot/runtime logs, diagnose firmware faults, send an explicitly approved serial diagnostic payload, or troubleshoot CH340 adapters, MCUs, Cool Pi, RK356x, or RK3588 devices.

Board Debug Assistant

Use the desktop application's existing session. Never open the serial port independently.

Start the conversation

1. Run these exact commands from the project root so project permissions can recognize the read-only operations:
   • powershell.exe -NoProfile -ExecutionPolicy Bypass -File skills/board-debug-assistant/scripts/board-debug.ps1 list-ports
   • powershell.exe -NoProfile -ExecutionPolicy Bypass -File skills/board-debug-assistant/scripts/board-debug.ps1 app-status
2. Report the detected adapter and active desktop connection. Ask the user to open the application and connect the port if the bridge is unavailable or disconnected.
3. Ask one focused question: what board is connected and what symptom should be diagnosed?
4. Ask only the next missing detail, such as expected behavior, reproduction step, baud rate, board power state, or recent firmware change.
5. Default to read-only analysis. State the working hypothesis and next observation before acting.

Observe and diagnose

1. From the project root, run powershell.exe -NoProfile -ExecutionPolicy Bypass -File skills/board-debug-assistant/scripts/board-debug.ps1 logs -Limit 200 for recent context.
2. Run powershell.exe -NoProfile -ExecutionPolicy Bypass -File skills/board-debug-assistant/scripts/board-debug.ps1 observe -Seconds 10 while the user reproduces the problem. Extend the window only when evidence is incomplete.
3. Correlate complete lines, timestamps, resets, repeated errors, register values, and command responses.
4. Separate observations from hypotheses and quote only the minimum relevant lines.
5. Ask the user for the next reproduction action when the log evidence is insufficient.

Request a serial write

Read references/safety.md and references/bridge.md before sending anything.

1. Show the exact port, text or HEX payload, and line ending.
2. Ask for explicit approval for that single payload.
3. Only after approval, invoke powershell.exe -NoProfile -ExecutionPolicy Bypass -File skills/board-debug-assistant/scripts/board-debug.ps1 send ... -Approved from the project root.
4. Read the resulting TX/RX logs and report the observed response.

Do not treat approval for one payload as approval for another. Never use -Approved based on inferred permission.

Current scope

Serial status, buffered logs, timed observation, approved serial writes, and audit inspection are implemented. SSH execution remains unavailable; report it as an unimplemented capability rather than bypassing the desktop application.