What problem does it solve?
Rushed, guesswork debugging is a leading cause of recurring bugs and wasted development time, as teams often fix symptoms instead of underlying root causes. This Skill enforces a strict, evidence-based protocol to eliminate guesswork and ensure fixes address the actual source of issues.
Core Features & Use Cases
- Scoped Investigation Lock: Freezes analysis to the affected module to prevent sprawling, unproductive exploration.
- Enforced No-Fix Rule: Blocks all code editing tools until a root cause is confirmed, preventing premature changes.
- Learning Capture: Automatically documents investigation findings to build organizational knowledge and avoid repeating past mistakes.
- Use Case: When an API endpoint returns intermittent 500 errors, this Skill guides you to trace the full data flow, form evidence-based hypotheses, and only implement a fix once the exact root cause (e.g., an unawaited database write) is confirmed.
Quick Start
Use the investigate skill to trace the root cause of the intermittent 500 errors returned by the POST /api/users endpoint, following the scoped investigation protocol without making any code changes until the root cause is confirmed.
