Reproduce failing tests and runtime errors to prove root causes with file:line evidence.
npx skills add https://github.com/arbazkhan971/godmode --skill debug-arbazkhan971
Please help me install this Agent Skill. Skill: debug Source: https://github.com/arbazkhan971/godmode/tree/main/skills/debug Command: npx skills add https://github.com/arbazkhan971/godmode --skill debug-arbazkhan971
This Skill eliminates guesswork when tests or runtime behavior fail by enforcing a reproduce → investigate → prove discipline that finds, documents, and verifies root causes with concrete evidence.
Run the debug loop on the failing test command, reproduce the failure three times, pick an investigation technique (stack trace, git bisect, or state inspection), prove the root cause with file:line and actual vs expected values, and either apply a one-line fix or hand off to /godmode:fix.
High-intent search queries and answers about installing and using this skill.
To debug failing tests and runtime errors, reproduce the failure three times to distinguish deterministic bugs from flaky ones, then apply stack trace analysis, git bisect, or state inspection to prove the root cause with file:line evidence.
The best way to use git bisect for intermittent test failures is to run the failing command multiple times to confirm the flaky behavior, then apply git bisect as a binary search technique with a strict 5-minute timeout per investigation step.
To document root causes when bug hunting, perform at least three "why" steps to prove the failure, collect file:line evidence with actual-vs-expected values, and append the structured findings to the .godmode/debug-findings.tsv file.
When your debugging technique gets stuck on a runtime error, the investigation enforces a strict 5-minute-per-technique timeout, skips the stuck bug, rolls back on catastrophic failure, and classifies it for future lessons.
Yes, this debugging approach handles both deterministic and flaky CI test failures by reliably reproducing the failing command multiple times to distinguish the failure type before choosing an investigation technique.
vadimcomanescuDiagnose software and runtime errors to identify root causes.
majedsiefalnasrDiagnose and fix failing GitHub Actions PR checks using gh CLI commands.
lhpaulAutomate GitHub PR review and CI verification workflows.
Nerfherder16Diagnose code or test failures using an 8-step structured investigation loop.
