debug-investigator

1. Trigger Conditions

Invoke this skill when:

• A bug, error, or regression is reported (error message, Slack thread, screenshot, network trace)
• A test is failing with no obvious cause
• A performance regression is observed and needs root-cause analysis
• The user says "debug this", "why is X broken", or "investigate this issue"

2. Prerequisites

• Symptom clearly described (error message, screenshot, or behavioral description)
• Access to the affected codebase
• Lint and typecheck commands available (npm run lint, npx tsc --noEmit)

3. Steps

Step 1: Reproduce and Understand

Gather the symptom — do not start searching code until the failure is understood: