What problem does it solve?
Debugging complex bugs often involves scattered guesswork and lost context between investigation rounds. This Skill structures the process by generating testable hypotheses, instrumenting code with NDJSON logging, and maintaining an evolving understanding document that records evidence, corrections, and lessons learned.
Core Features & Use Cases
- Hypothesis-Driven Investigation: Generates 3-5 testable hypotheses from the bug description, each with logging points and confirm/reject evidence criteria.
- Documented Exploration: Maintains understanding.md with an iteration timeline, corrected misunderstandings (strikethrough annotations), and a consolidated current-state summary.
- Session Persistence: Stores debug.log, hypotheses.json, and understanding.md under .workflow/.debug/ so sessions resume across Explore, Analyze, and Fix modes.
- Use Case: You hit an intermittent 'config value is None' error. Run the skill to instrument the suspected code paths, reproduce the bug, then let it parse the NDJSON log, confirm the root-cause hypothesis, apply the fix, and clean up all instrumentation.
Quick Start
Ask the AI to debug the error message you are seeing using the debug-with-file workflow, then reproduce the bug and run it again for analysis.