Diagnose hard bugs through reproduction, bisection, and debugger configuration generation.
npx skills add https://github.com/avbel/ai-skills --skill dev-debug-avbel
Please help me install this Agent Skill. Skill: dev-debug Source: https://github.com/avbel/ai-skills/tree/main/skills/dev-debug Command: npx skills add https://github.com/avbel/ai-skills --skill dev-debug-avbel
High-intent search queries and answers about installing and using this skill.
Build a deterministic failing command first — a test, curl call, or git bisect run wrapper — then list 3-5 falsifiable hypotheses and test only the top one with runtime evidence. Never write a fix before confirming the root cause.
For Node, create a launch.json entry of type node pointing at the test binary, or run node --inspect-brk with chrome://inspect. For Rust, build with cargo test --no-run and debug the binary via CodeLLDB or rust-lldb with breakpoints at file:line.
Use rr record and rr replay on Linux to reverse-continue from the crash back to the cause, since debugger pauses can mask races. Alternatively, add timestamped logging with thread IDs and reconstruct the interleaving.
Use git bisect run with your failing command whenever a regression spans more than a handful of commits. It mechanically finds the exact offending commit, which is faster and more reliable than reading diffs manually.
Print debugging fails when state mutates unexpectedly, timing matters, or the failure point is far from the cause. After two failed hypotheses, switch to an interactive debugger with conditional breakpoints at the suspect locations.
DennisTomaDetect Jest, Vitest, Pytest, Go, and Cargo tests and run them.
divad12Write a failing regression test before tracing the root cause and fixing the bug.
TMI-appsRemove temporary console logs, instrumentation, and legacy code from codebases.
hafiznaveedchuhan-ctrlGuide software bug investigations through structured phases from data collection to fix implementation.
