bug-hunter

Structured bug investigation begins by collecting symptoms, reproduction steps, and environment details. This Skill guides you through gathering evidence systematically—analyzing logs, stack traces, and minimal reproducible examples—then applies root cause analysis techniques like 5 Whys to identify the underlying issue rather than just the surface symptom.

Root cause analysis applies structured techniques like Fishbone diagrams and the 5 Whys method to trace failures back to their origin. This Skill walks through log and stack-trace analysis, hypothesis testing, and failure-mode identification to pinpoint the actual cause so fixes address the problem, not just symptoms.

After diagnosis, this Skill proposes short-term, medium-term, and long-term solutions with code examples and implementation steps. It produces actionable fix proposals backed by evidence gathering and verification steps, reducing the gap between identifying a problem and deploying a corrective action.

Yes. This Skill applies across debugging sessions by collecting environment details, reproduction steps, and system context. It handles log and stack-trace analysis, minimal reproducible examples, and structured RCA workflows—satisfying requirements for reproducibility, evidence gathering, and consistent debugging across different conditions.

Effective bug investigation requires symptoms, reproduction steps, environment details, logs, and stack traces. This Skill guides structured collection of this input data, helping you create minimal reproducible examples and gather evidence needed to apply hypothesis testing and debugging tools accurately.

This Skill streamlines debugging by automating the investigation workflow—guiding evidence collection, applying proven RCA techniques, and generating fix proposals with implementation steps. It eliminates manual trial-and-error, allowing developers to move faster from problem report to corrective action and system restoration.