investigate

Root-cause debugging requires gathering evidence from logs and stack traces before applying fixes. This Skill enforces a four-phase workflow—investigate, analyze, hypothesize, implement—to systematically diagnose why code is broken using tools like grep and web search.

Systematic troubleshooting prevents premature fixes by enforcing evidence gathering. This Skill proactively engages when you report errors or unexpected behavior, guiding you through investigation and analysis to identify the actual root cause before remediation.

Fixing stack traces deterministically requires reading the error context and gathering evidence first. This Skill enforces an Iron Law of no fixes without root cause, ensuring you analyze logs and hypothesize correctly before implementing any code changes.

Yes, the debugging workflow applies broadly to software engineering bugs. It triggers whenever you request bug fixes or ask why something is broken, using Bash, Read, Write, Edit, Grep, and Glob to perform deterministic tasks and surface the root cause.

Code breaks after quick patches because the root cause was never identified. This Skill solves that by enforcing a strict four-phase workflow—investigate, analyze, hypothesize, implement—ensuring you gather evidence and confirm the root cause before applying remediation.