investigate

Root cause analysis in software debugging identifies the true origin of issues by collecting symptoms and reading code to avoid chasing surface-level errors. This skill applies a structured, evidence-based workflow to trace complex software issues across modules and environments.

Debug a complex software issue across modules by following a guided flow: collect symptoms and logs, read code for pattern analysis, form testable hypotheses, and verify them with controlled experiments. This systematic approach reduces time spent chasing symptoms.

The best way to structure a debugging workflow is to follow deterministic phases: investigate, analyze, hypothesize, and implement. Start by describing observed symptoms and reproduction steps, then use evidence-based hypothesis testing to verify solutions before producing a fix.

Yes, you can use hypothesis testing to verify a software bug fix by forming testable hypotheses about the root cause and validating them through controlled experiments. This evidence-based approach ensures the solution addresses the actual origin rather than just masking symptoms.

Systematic troubleshooting works for issues across different environments by applying a structured investigation workflow that collects data and reads code regardless of the deployment context. It guides users from observed symptoms to reliable fixes across complex software modules.

You should use code reading for troubleshooting because it enables pattern analysis to identify actual root causes, avoiding the guesswork that wastes time chasing symptoms. This skill requires structured data collection and evidence-based hypothesis testing to verify reliable fixes.