vc:debug

Root-cause debugging identifies the underlying source of bugs, test failures, and system incidents before applying fixes. You need it for CI/CD pipeline failures, performance slowdowns, and multi-component integration issues to stop recurring problems.

Debug system incidents by applying a four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation. This workflow reveals the true root cause behind failures before you implement and validate fixes.

Verify a bug fix using defense-in-depth validation by checking across entry points, business logic, environment guards, and instrumentation. Emphasize evidence-based completion with fresh verification data and documentation before closing the issue.

Yes, this debugging workflow orchestrates end-to-end investigation for code-level, system-level, and CI/CD scenarios. It applies to performance slowdowns, integration issues, and multi-component failures to reveal the root cause.

The best way to investigate test failures is following a structured root cause investigation, pattern analysis, and hypothesis testing process. This evidence-based approach ensures you fix the source rather than applying superficial patches.

Repeated bug fixes fail when the root cause is not fully investigated across entry points, business logic, and environment guards. Defense-in-depth validation with fresh verification data is required to confirm the fix before completion.