What problem does it solve?
Systematically investigate and resolve software and system failures by tracing root causes before applying fixes, preventing wasted effort and regressions.
Core Features & Use Cases
- Systematic four-phase debugging workflow: investigation, pattern analysis, hypothesis testing, implementation.
- Root-cause tracing through call stacks and test bisection, including a bisection script to find polluting tests.
- Defense-in-depth validation across entry points, business logic, environment guards, and debug instrumentation.
- Log and CI/CD analysis, performance diagnostics, database forensics, structured investigation reports, and task-managed investigation pipelines.
- Use cases: flaky tests and test pollution, CI failures, server 500s, slow queries, multi-service incidents, and frontend visual regressions.
Quick Start
Ask ck:debug to investigate "500 errors on /api/orders" providing stack traces, CI logs, recent commits, and reproduction steps and request root cause, mitigation, and verification steps.