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.
- skills.sh installs
- 2.8K
- GitHub stars
- 195.3K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add microsoft/vscode --skill fix-errors --agent claude-codeInstalls into .claude/skills of the current project.
Files
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.
Browse the repository on GitHubSponsors
Agent CaffeineSponsoredClose your lid, come back to finished work
SnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthly
WaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthly
knobsSponsoredSee your site on any phone, any day, in any languageDetails
- Repository
- github.com/microsoft/vscode
- Category
- Debugging
- First seen
- Apr 16, 2026
More from microsoft/vscode
All 15Recommended
More Debugging
chrome-mcp-troubleshootingtrailofbits/skillsDiagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", 2.7Kskills.sh installsclaude-in-chrome-troubleshootingtrailofbits/skillsDiagnose and fix Claude in Chrome MCP extension connectivity issues. Use when mcp__claude-in-chrome__* tools fail, return "Browser extension is not connected", 2.6Kskills.sh installs
export-download-debuggingnexu-io/open-designDiagnose and fix browser, preview, or Electron export/download failures, especially image export issues involving Save As, Blob/Data URLs, the File System Acces1.9Kskills.sh installs
correctness-and-error-handlingcognitedata/builder-skillsMUST be used whenever fixing correctness and error handling issues in a Flows app. This skill finds AND fixes bugs, missing error states, unhandled rejections, 1.9Kskills.sh installs
flowstudio-power-automate-debuggithub/awesome-copilotDebug failing Power Automate cloud flows using the FlowStudio MCP server. The Graph API only shows top-level status codes. This skill gives your agent action-le1.9Kskills.sh installs
gitnexus-debuggingabhigyanpatwari/gitnexusUse when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace1.8Kskills.sh installs