The Problem

Most developers debug reactively — they see an error and start guessing. A systematic approach saves hours.

The Prompt

Analyze this error systematically:
1. First, reproduce the exact error
2. Identify the error type and origin
3. Trace the execution path
4. Propose 3 possible root causes ranked by likelihood
5. Suggest the minimal fix for each cause

Error: [paste your error here]
Context: [describe what you were doing]

When to Use

Use this skill when you encounter an error you cannot immediately explain. Works best with stack traces, error messages, or unexpected behavior descriptions.