When a bug has many possible causes, it can be hard to find the real problem. This method helps you test several ideas at once. You collect evidence and decide which cause is most likely.
You start by listing different hypotheses for what went wrong. Then you gather facts from code, logs, and tests. Each piece of evidence makes one hypothesis stronger or weaker.
At the end you pick the best explanation with the most proof. This approach stops you from jumping to conclusions. It works well for tricky bugs that cross multiple parts of a system.
Global
mkdir -p ~/.claude/skills/parallel-debuggingProject
mkdir -p .claude/skills/parallel-debuggingSource 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