hapo:debug

Root-cause diagnosis requires an evidence-first approach that systematically analyzes codebase context, evidence, and blast radius before forming hypotheses. This ensures you address the underlying cause rather than just treating symptoms.

Evidence-first debugging prioritizes gathering and analyzing concrete data before attempting fixes. Use this structured diagnosis process for complex software issues where superficial symptom treatment has failed or risks introducing regressions.

Start debugging an issue by providing the specific problem context to trigger a scout-first investigation of the codebase. This methodology mandates thorough code inspection to gather evidence before creating a verification plan.

Yes, this root-cause analysis approach supports frontend and performance issues, alongside general CI and quick debugging contexts. It adapts its systematic codebase inspection and evidence gathering to these specific software engineering scenarios.

The best way to verify a software fix is to follow a detailed verification plan generated after root-cause identification. This structured plan confirms the fix resolves the issue completely without introducing unintended side effects.

Your software issue likely recurs because the fix addressed symptoms rather than the root cause. An evidence-first diagnosis process analyzes the codebase context and blast radius to ensure the underlying problem is fully resolved.