lubochka Failure Triage
Purpose
Classify failures before changing implementation.
When to Use
Use after failed builds, tests, commands, or smoke checks.
Inputs
Failure output, environment, recent changes, expected behavior.
Steps
- Capture the symptom.
- Classify likely source: code, test, environment, data, flaky behavior, or command misuse.
- Choose the smallest next check.
- Avoid broad rewrites until cause is narrowed.
Gates
There is a probable cause and next diagnostic step.
Evidence
Failure logs, narrowed hypothesis, and targeted check result.
Anti-Patterns
Fixing blindly; changing multiple variables at once.
Related
root-cause-tracing, systematic-debugging