Turn a bug symptom into a fix with a regression test that locks it down. If the user opens vague ("there's a bug", "/diagnose"), interview them one question at a time until you have enough to attempt a reproduction; if you still cannot reproduce, say so explicitly. Then drive the work through five phases — build a deterministic feedback loop, reproduce, hypothesise, probe, write a spec — and hand off to TDD for the regression test. Trigger when the user reports something broken, slow, wrong, or regressed: "X is failing", "this throws", "something regressed", "diagnose this", "debug this", "investigate why...".
$npx -y skills add eduwxyz/my-awesome-skills --skill diagnoseInstalls into the current project.
Run `npx skills use "https://github.com/eduwxyz/my-awesome-skills" --skill "eduwxyz/my-awesome-skills/diagnose"` 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/eduwxyz/my-awesome-skills" that are relevant to the current task. Run `npx skills add "https://github.com/eduwxyz/my-awesome-skills"` and select the relevant skills, then follow their instructions.