01
What this skill does
Use this skill when code reading is not enough. It forces hypotheses, logging, reproduction, root-cause notes, and post-fix verification before cleanup. The bundled collector can capture browser or app logs into NDJSON and expose a same-origin dashboard for live inspection, then final cleanup removes collector artifacts and the root-cause document unless evidence retention is requested.
02
When to use it
- SignalFrontend issues where browser logs need to reach an active collector directly.
- SignalRuntime failures that are easy to guess about but hard to prove from static code.
- SignalFlaky behavior that needs timestamped evidence and before/after comparison.
03
How it works
- 01
State precise hypotheses before instrumenting.
- 02
Attach to an existing logging session or start the bundled collector.
- 03
Add minimal temporary instrumentation tied to each hypothesis.
- 04
Reproduce the issue, inspect the recorded log file, and mark hypotheses as confirmed, rejected, or inconclusive.
- 05
Apply only proven fixes, then collect fresh post-fix logs before removing instrumentation.
04
What you get back
- SignalA root-cause document that evolves during investigation and is deleted after successful final cleanup unless retained by request.
- SignalTemporary instrumentation plus collector, log, and root-cause document cleanup.
- SignalA verified fix backed by fresh runtime logs.
05
Important boundaries
- SignalDo not ship speculative fixes without runtime proof.
- SignalDo not create app-local proxy APIs for browser logs unless direct collector delivery is proven blocked.
- SignalKeep root-cause documents through intermediate log clears, then delete them during final successful cleanup unless the user asks to retain evidence.
06