Diagnose hard bugs and performance regressions with reproducible feedback loops.
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill diagnose-ayehiaa
Please help me install this Agent Skill. Skill: diagnose Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.claude/skills/diagnose Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill diagnose-ayehiaa
This Skill helps you systematically diagnose hard bugs and performance regressions by turning vague failures into a repeatable feedback loop with crisp verification.
Ask to diagnose a specific failing scenario and provide a repro signal (error message, failing command, captured trace/logs, or a test case) so the Skill can drive the reproduce → hypothesize → instrument → fix → regression-test process.
High-intent search queries and answers about installing and using this skill.
Debugging hard bugs requires a reproducible feedback loop with a sharp pass/fail signal, using staged testing and falsifiable ranked hypotheses to verify fixes. You reproduce the exact symptom, generate hypotheses, instrument with probes, then fix and lock in regression tests.
Hypothesis-driven verification for performance regression testing involves creating falsifiable ranked hypotheses to systematically isolate measurable slowdowns, using minimally invasive instrumentation and trace replay to confirm the exact cause before applying fixes.
Diagnosing a flaky bug involves raising reproduction rates by building a deterministic debugging signal from failing tests, scripts, CLI fixtures, or trace replay, then applying structured loops rather than guesswork to systematically verify staged hypotheses.
You should stop debugging a failing test when no reliable reproducible loop can be constructed. The process explicitly halts as a safety gate and requests concrete artifacts, captured traces, or access needed to proceed, preventing guesswork without a sharp pass/fail signal.
To start debugging recurring exceptions you need a reproducible signal such as an error message, failing command, captured trace, logs, or a test case. This input artifact is required to drive the reproduce, hypothesize, instrument, and fix workflow effectively.
The best way to lock in fixes for performance regressions is to enforce regression-test locking after applying fixes, ensuring the measurable slowdowns are provably corrected through a deterministic feedback loop with crisp verification and staged testing.
TrebuchetDynamicsDiagnose hard bugs and performance regressions through an evidence-driven feedback loop.
tomgunReproduce bugs with regression tests and apply minimal root-cause fixes.
xiaoshuangLiDiagnose software defects through reproduction, hypothesis testing, and verification.
JNZaderAutomate hypothesis-driven debugging with tagged logs and automated cleanup.
