What problem does it solve? Bug reports arrive in many forms — stack traces, failing tests, vague descriptions, or unverified suspicions — and ad-hoc fixing often skips reproduction, regression tests, or root-cause analysis. This Skill orchestrates a disciplined debugging pipeline that reproduces the issue, diagnoses the root cause, writes a failing regression test, applies a minimal fix, and verifies it with review. ## Core Features & Use Cases - Two certainty modes: certainty:high runs a full TDD bug-fix pipeline (reproduce → diagnose → approval gate → regression test → fix → verify → review); certainty:low runs a read-only hypothesis investigation that proves or disproves a suspicion with exploratory tests and a verdict report. - Flexible input handling: accepts free-text bug reports, stack traces, error messages, failing test names, and GitHub issue URLs, with untrusted-content isolation for external input. - Domain research integration: conditionally dispatches web research agents when bugs involve external APIs, protocols, or library behavior. - Use Case: A user reports "the WebSocket reconnection fails on timeout" — the pipeline reproduces the failure, diagnoses the root cause with file:line precision, gets user approval, writes a failing regression test, applies a minimal fix, and delivers a verified report. ## Quick Start Ask the assistant to debug the failing payment test and fix the root cause with a regression test.
