Fix Errors

When you're staring at a telemetry dashboard full of stack traces, this walks you through the investigation process that experienced VS Code contributors actually use. The core insight is counterintuitive: don't fix errors where they crash. Instead, trace the call stack upward to find whoever produced the invalid data in the first place. It covers the distinction between producers and consumers, when to enrich error messages with diagnostic context instead of swallowing errors, and how to read error construction code to understand what you're actually dealing with. The listener leak example is especially good, showing how a "dominated" leak versus "popular" leak changes your entire fix strategy.

Install to Claude Code

npx -y skills add microsoft/vscode --skill fix-errors --agent claude-code