⚡AgentSkills
🧰 Engineering Essentials · Debugging Craft

Hunt bugs systematically (C++)

Reproduce, bisect, hypothesize, verify — the method that beats random poking under deadline pressure.

foundation~30 minAll Software Engineers

Steps

  1. 1Reproduce deterministically first; flaky repro = flaky fix
  2. 2Write failing test capturing the bug before touching source
  3. 3Bisect history or code path until minimal failing case remains
  4. 4Form ONE hypothesis, predict its observable, then check
  5. 5Fix root cause, not nearest symptom; add regression test
  6. 6Document the hunt briefly for future searchers
  7. 7Sanitizer builds (ASan/UBSan) in CI before perf tuning
  8. 8Profile with perf/VTune; watch cache lines and allocations

Common Pitfalls

  • ▲Shotgun changes stacking unknown unknowns
  • ▲Fixing symptoms while root cause ships elsewhere

Commands

Install with skills CLI
$ npx skills add aniruddhaadak80/skills --skill debug-craft-systematic-bug-hunt-cpp
Install globally
$ npx skills add aniruddhaadak80/skills --skill debug-craft-systematic-bug-hunt-cpp -g

Tags

#debugging#methodology#engineering-essentials#debug-craft

Related skills

Reproduce, bisect, hypothesize, verify — the method that beats random poking under deadline pressure.

🧰 Engineering Essentials·~30m

Reproduce, bisect, hypothesize, verify — the method that beats random poking under deadline pressure.

🧰 Engineering Essentials·~30m

Reproduce, bisect, hypothesize, verify — the method that beats random poking under deadline pressure.

🧰 Engineering Essentials·~30m