Every error message in the VS Code telemetry dashboard points to a crash. But the fix is rarely at the crash site. Instead, you need to trace the data flow back to the producer of the invalid data.
This guide shows you how to read a stack trace from bottom to top. You will learn to find where the bad data comes from and fix it there. You will also learn to enrich error messages with helpful details so the next crash gives you the information you need.
Most importantly, you will avoid the common mistake of silently hiding errors. That only delays the problem. The right approach fixes the root cause and makes the system more reliable.
Global
mkdir -p ~/.claude/skills/fix-errorsProject
mkdir -p .claude/skills/fix-errorsSource Repository
Azure Diagnosticsmicrosoft/azure-skills
Debug Azure production issues with systematic diagnostics and AI-powered tools
Azure Messagingmicrosoft/azure-skills
Troubleshoot and fix Azure messaging SDK errors for Event Hubs and Service Bus
Use My Browserxixu-me/skills
Work inside your live browser session for real page inspection and debugging
Diagnosemattpocock/skills
A step-by-step debug loop for finding and fixing hard bugs
Diagnosing Bugsmattpocock/skills
Build a tight feedback loop to find any bug fast
Systematic Debuggingobra/superpowers
Find the root cause of every bug before attempting any fix to save time
Safe Debuglllllllama/rigorpilot-skills
Debug deep learning failures safely with conservative diagnosis and minimal patches
Firebase Crashlyticsfirebase/agent-skills
Set up crash reporting for your Android or iOS app with ease