When something breaks in your code, do not guess. A systematic approach saves time and avoids more problems. This method helps you find the root cause of any error.
Use the Stop-the-Line Rule to stop adding new features and preserve all evidence. Then follow the Triage Checklist step by step. You will reproduce the bug, localize where it happens, and reduce it to the smallest failing case.
This process works for test failures, build errors, runtime bugs, and production incidents. It helps developers, testers, and anyone who writes code fix problems with confidence.
Global
mkdir -p ~/.claude/skills/debugging-and-error-recoveryProject
mkdir -p .claude/skills/debugging-and-error-recoverySource 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
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
Python Performance Optimizationwshobson/agents
Profile and optimize Python code to find and fix performance bottlenecks quickly