When a bug is found, the real cause must be uncovered. This skill reads the bug report and then inspects the actual code to find the root cause. It does not guess or rely on assumptions. The analysis must be based on what the code really does.
After finding the cause, the skill evaluates how many other parts of the software could be affected. It then suggests two or three fix options with their pros and cons. The developer can decide which approach to take. No code is changed during this step.
This careful process helps fix bugs correctly the first time. Developers save time and avoid introducing new problems.
Global
mkdir -p ~/.claude/skills/cs-issue-analyzeProject
mkdir -p .claude/skills/cs-issue-analyzeSource 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