Bug Finding Methodology

Root cause analysis requires a systematic approach: reproduce the bug consistently, map the execution flow to identify all involved components, formulate probable causes ranked by likelihood, and propose verification steps using logging or testing. This prevents temporary fixes and ensures lasting solutions.

Start by clearly defining expected vs. observed behavior and reproduction steps. Visualize the execution flow using diagrams to pinpoint failure points. List your top 3 probable causes with confidence levels, then design a verification plan using standard tools like grep, logging, or network inspection to test each hypothesis.

Use a six-step systematic diagnostic workflow: define the bug precisely, visualize data and control flow, identify probable root causes, prioritize them by confidence, create a verification plan, and validate the fix with minimal, targeted changes. This prevents wasted effort on wrong assumptions.

Systematic root cause analysis applies to any bug context—development, bug reports, or production incidents. The methodology enforces reproducibility and validation before fixes, making it especially valuable for production where incorrect fixes carry higher risk.

Standard engineering tools suffice: read and grep for code inspection, glob for file discovery, bash for scripting, and logging or testing frameworks for hypothesis verification. The Skill teaches *how* to use these tools systematically rather than requiring specialized debugging software.

Flow visualization exposes all components involved and their interactions, revealing where failures can occur and which components to inspect first. This prevents blind investigation and helps prioritize probable causes by identifying which parts of the flow are most likely to contain the defect.