debug-detective

Systematically debug by following a five-step protocol: reproduce the bug consistently, isolate it to specific code or conditions, understand the root cause through analysis, apply a minimal fix, then verify the fix resolves the issue without side effects. This universal approach works across all languages and frameworks.

Yes. The universal debugging protocol applies to all codebases regardless of language or framework. It guides you through reproducibility, isolation, understanding, fixing, and verification—complemented by language-agnostic logging and tracing strategies.

Isolate intermittent and environment-specific failures by reproducing them consistently, then systematically narrow down the conditions triggering the issue. Use logging and tracing to capture state across different environments, then apply targeted fixes verified in each context.

Diagnose performance issues by reproducing the degradation, isolating the affected code paths through tracing and logging, understanding the bottleneck's root cause, fixing the inefficiency with minimal changes, then verifying improvement under real-world load.

No. The universal debugging protocol works without framework-specific tools. It provides language-agnostic steps, logging techniques, and analysis methods that apply to any codebase, though optional MCP-enabled analysis methods can enhance the workflow.