Back to skills
Diagnosis
Debug
/hapo:debug
Diagnostic-only root-cause workflow for bugs, failing tests, CI issues, performance issues, and UI regressions.
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 exact symptom, command, logs, stack trace, and environment facts.
03 / Patterns
Compare failing path with nearby working examples.
04 / Hypotheses
Test competing causes one variable at a time.
05 / Root cause
Trace file/line or config source and explain why now.
06 / Plan
Define blast radius and verification checks for the fix.
Output
A root-cause contract ready for `/hapo:hotfix` or implementation work.
Avoid
Do not edit product code while diagnosing except temporary instrumentation that is removed before handoff.
Next Handoff
/hapo:hotfix