debug

Root cause analysis for persistent failures requires gathering symptoms, expected behavior, actual behavior, and trigger points before proposing a fix. This approach stops repeated guessing by verifying findings against prior errors, relevant files, and test outcomes to isolate the true cause.

A circuit breaker workflow in debugging activates an isolated investigation process after three consecutive failures on the same problem. It stops repeated guessing by offloading heavy codebase investigation, checking prior errors, and forming a confidence-rated diagnosis before any repair.

Systematically debug recurring errors by gathering symptoms and trigger points, searching the codebase, and verifying findings against test outcomes. This methodical failure diagnostics process requires user approval, test execution, and regression checks before considering the issue resolved.

Use a subagent for error diagnostics when persistent failures require heavy codebase investigation. An isolated debug agent checks prior errors, searches relevant files, and forms a confidence-rated triage, ensuring you verify findings before recommending a fix rather than guessing.

This debugging method requires test execution and regression checks before considering an issue resolved. It verifies the confidence-rated diagnosis against existing test outcomes and relevant files, ensuring the recommended fix addresses the actual root cause without introducing new failures.