investigate
A structured debugging workflow that enforces root cause analysis before any fix is applied.
Setup & Installation
What This Skill Does
A structured debugging workflow that enforces root cause analysis before any fix is applied. It runs four phases: investigate, analyze, hypothesize, implement. The core rule is simple: no code changes until the root cause is confirmed.
Instead of patching symptoms and creating whack-a-mole bugs, this enforces a confirmed root cause before touching any code, which means fixes actually stick.
When to use it
- Tracing why a regression appeared after a recent commit
- Debugging intermittent failures that only show up in staging
- Finding the root cause of a null reference before patching it
- Running a structured post-mortem on a bug that keeps coming back
- Diagnosing configuration drift between local and production environments
Similar Skills
wp-phpstan
Configures and runs PHPStan static analysis in WordPress codebases.
web-quality-audit
Runs a web quality audit across performance, accessibility, SEO, and best practices based on Google Lighthouse checks.
core-web-vitals
Diagnoses and fixes Core Web Vitals issues across LCP, INP, and CLS.
webapp-testing
Automates interaction with local web applications using Python Playwright.
