debug-tools

Iterative debugging automates root cause analysis for intermittent runtime failures by strategically injecting 3-5 logs, scoring investigation confidence, and proposing minimal fixes to isolate the exact issue.

Targeted runtime inspection finds silent errors across client-side apps and APIs by injecting strategically placed logs during an automated debugging session, then automatically cleaning them up post-resolution.

Confidence scoring in debugging workflows prioritizes root cause investigations by evaluating the likelihood of identified issues, helping determine next steps and whether to proceed to log injection or propose a fix.

MCP servers are optional for runtime inspection debugging; the workflow supports optional MCP integration to adapt to available runtime analysis tools, but requires YAML frontmatter metadata for activation.

Automated log injection and cleanup during codebase debugging works through a five-phase workflow: Investigate, Inject Logs, Propose Fix, Verify, and Cleanup, ensuring targeted logs leave no traces post-resolution.

The debugging workflow handles intermittent failures in complex codebases by standardizing the debugging process with confidence-scored analysis and structured log injection, targeting runtime issues across APIs and client-side apps.