Guide a 6-phase workflow to reproduce, diagnose, and fix software bugs.
npx skills add https://github.com/kyo0221/claude-config --skill diagnose-kyo0221
Please help me install this Agent Skill. Skill: diagnose Source: https://github.com/kyo0221/claude-config/tree/main/skills/diagnose Command: npx skills add https://github.com/kyo0221/claude-config --skill diagnose-kyo0221
This Skill eliminates unproductive, guesswork-driven debugging of complex, hard-to-reproduce software bugs and performance regressions that waste developer time and often lead to incomplete or incorrect fixes.
Use the diagnose skill to apply the disciplined 6-phase workflow to debug the reported intermittent checkout failure that only occurs during peak traffic.
High-intent search queries and answers about installing and using this skill.
To debug hard-to-reproduce software bugs and performance regressions effectively, use a structured 6-phase workflow that builds deterministic reproduction loops, generates falsifiable hypotheses, instruments code, and implements regression tests to replace guesswork.
Building a deterministic reproduction loop for non-deterministic bugs requires applying ranked strategies to create fast, agent-runnable pass/fail signals, ensuring consistent replication of runtime errors and unexpected application behavior before generating testable hypotheses.
Fixing a performance regression in a production API without a clear root cause involves building a repro harness, generating falsifiable hypotheses, instrumenting code for targeted debugging, and implementing a fix alongside regression tests to prevent recurrence.
Systematic hypothesis testing works for resolving intermittent application failures by providing a disciplined workflow to generate falsifiable hypotheses and instrument code, eliminating inefficient guesswork when dealing with unexpected application behavior.
You should not use guesswork-driven debugging for runtime errors when encountering complex failing tests or performance slowdowns that cannot be resolved via simple code inspection, as this often leads to incomplete fixes and wasted developer time.
You need regression testing after fixing complex software bugs to validate the implemented fix, ensure the failing tests pass deterministically, and perform post-mortem analysis that prevents future occurrences of the same performance regressions.
derHakenTrace data flow and apply a four-phase process to fix root causes.
MichaelSolatiGuide structured 6-phase debugging for elusive bugs and performance regressions.
JeromyJSmithDiagnose hard bugs and performance regressions with a deterministic pass/fail feedback loop.
amano--Analyze code for bugs, standards, and security vulnerabilities across languages.
