ck:debug

To find the root cause of a CI/CD failure, use an evidence-driven investigation process that traces backward call-chains and analyzes logs before attempting fixes. This separates pattern analysis and hypothesis testing from implementation.

Debugging performance regressions across components requires layered validation and backward call-chain tracing to pinpoint the exact source. A structured diagnostic report ensures remediation is backed by fresh verification evidence.

Tracing a test failure that pollutes state requires systematic debugging flow, isolating investigation from implementation. You trace the root cause through layered validation and verify the fix with fresh evidence to ensure the defect is resolved.

Yes, npm is required as a dependency to run the scripts and references used by this debugging workflow. You need the environment setup to execute the systematic investigation phases and generate structured diagnostic reports.

Tracing backward call-chains instead of fixing immediately prevents patching symptoms while leaving the underlying defect intact. Evidence-driven investigation ensures your remediation targets the true root cause, verified through fresh validation.