Isolate bug causes through reproducible feedback loops and hypothesis testing.
npx skills add https://github.com/kartikkabadi/skills --skill diagnose-kartikkabadi
Please help me install this Agent Skill. Skill: diagnose Source: https://github.com/kartikkabadi/skills/tree/main/diagnose Command: npx skills add https://github.com/kartikkabadi/skills --skill diagnose-kartikkabadi
Diagnose helps you systematically investigate bugs, regressions, and performance problems instead of guessing. It creates a reliable feedback loop so you can reproduce the issue, narrow the cause, and verify the fix.
Use the diagnose skill to reproduce the bug, propose ranked hypotheses, and build a minimal regression test for the failure.
High-intent search queries and answers about installing and using this skill.
Systematically debug flaky tests by building a deterministic reproduction loop first, then ranking falsifiable hypotheses and instrumenting one variable at a time to isolate the cause. This prevents guessing and confirms the fix with a regression test.
Hypothesis-driven debugging isolates code regressions by ranking possible causes and testing them one by one through targeted instrumentation. You eliminate incorrect assumptions sequentially until the root cause is confirmed and validated.
Trace performance regressions across CLI, API, and UI workflows by establishing reproducible feedback loops with traces or scripts. You propose ranked hypotheses, instrument specific bottlenecks, and verify the slowdown is resolved.
Diagnosing broken behavior requires deterministic reproduction steps as a prerequisite. You must build a reliable feedback loop using tests, scripts, or harnesses before changing code to ensure you can accurately isolate the cause.
The best way to fix hard bugs without randomly changing code is reproduction-first debugging. You build a minimal failing test that reproduces the defect, apply the fix at the correct seam, and rerun the scenario to confirm the bug is gone.
You should avoid a systematic debugging approach when you lack reproducible steps or when the defect stems from obvious syntax errors or missing dependencies that are immediately identifiable from standard stack traces.
deathbeamGuide six-phase debugging to isolate software defects and performance regressions.
Agentic-AssetsIdentify and isolate software root causes through structured reproduction and hypothesis testing.
ArabelaTsoInstrument source code in Python, Java, JavaScript, and C/C++ to collect runtime information.
OrestesKDiagnose software bugs and performance regressions through a disciplined feedback loop.
