Back to skills
Diagnosis
Debug
/cf:debug
Adaptive-depth, diagnostic-only root-cause workflow for local failures and complex incidents.
Use When
- Root cause is unknown.
- A test, build, CI job, UI flow, or production behavior fails.
- You need evidence before changing code.
Flow
01 / Scout
Map affected files, callers, runtime, config, tests, and recent changes.
02 / Evidence
Capture the failing baseline; add a correlated timeline for deep incidents.
03 / Eliminate
Test competing causes and preserve why each candidate remains or is removed.
04 / Trace
Separate trigger, root cause, and contributing factors back to the earliest owned invariant.
05 / Handoff
Define blast radius, verification, side effects, and recurrence-prevention gaps.
Output
An evidence-backed diagnosis and prevention-aware proof plan ready for `/cf:fix`.
Avoid
Do not edit product code while diagnosing except temporary instrumentation that is removed before handoff.
Next Handoff
/cf:fix