ethan826 · Agent Skills

ethan826

Community

root-cause-debugging

Finds the root cause of a bug before any fix is written, in four phases (investigate, compare against working code, test one hypothesis, fix at the source with a failing test first). Use it whenever a test fails, a build breaks, behavior surprises you, a bug report or ticket arrives, or a test "passes on rerun", and use it before proposing any fix, even one that looks obvious. It matters most under time pressure, after a fix has already failed, and when a failure looks flaky, environmental or "n

1h installs

1

GitHub stars

0

Updated

Oct 23