Step-by-step procedure for diagnosing and fixing failures — reproduce, read, hypothesize, bisect, fix, regression-test. Trigger this whenever something does not work as expected — a bug report, a failing or flaky test, a crash, an error message, wrong output, "it worked yesterday", or unexpected behavior during your own implementation. Trigger BEFORE proposing any fix. Do NOT trigger for building new features (use task-planning) or for the moment you realize your overall approach is wrong rather than the code (use course-correction).
$npx -y skills add unpaidattention/fable5-methodology --skill debugging-methodologyInstalls into the current project.
Run `npx skills use "https://github.com/unpaidattention/fable5-methodology" --skill "unpaidattention/fable5-methodology/debugging-methodology"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/unpaidattention/fable5-methodology" that are relevant to the current task. Run `npx skills add "https://github.com/unpaidattention/fable5-methodology"` and select the relevant skills, then follow their instructions.