skill-skills-opencode-debugging-techniques

Structured debugging identifies root causes by applying a hypothesis-first workflow, selectively instrumenting code, running scoped experiments, and validating fixes with concrete checks.

Hypothesis-driven debugging forms focused assumptions based on recurring symptoms before adding targeted instrumentation. Use it when symptoms repeat across software projects, services, or data pipelines.

Targeted instrumentation adds logs and readings only where they inform the current hypothesis, avoiding log spam. This scoped approach narrows the debugging cycle and isolates variables.

Yes, structured troubleshooting workflows apply to data pipeline failures. The pattern handles repeating symptoms across services by iteratively narrowing scope and validating hypotheses systematically.

The best way to validate a root cause fix is through iterative narrowing and concrete validation checks. This ensures the scoped experiment confirms the hypothesis and eliminates the recurring symptoms.