Use when encountering ANY bug, error, test failure, or unexpected behavior. Activate for keywords like "bug", "error", "failing", "broken", "doesn't work", "unexpected", "crash", "exception", "TypeError", "undefined", stack traces, or any error message. Also trigger when tests fail unexpectedly, when behavior differs from expectations, when investigating production incidents, or when flaky/intermittent issues appear. Investigation produces evidence and a written hypothesis before any fix is attempted. Always investigate root cause before proposing fixes -- never guess at solutions.
$npx -y skills add duthaho/claudekit --skill investigate-root-causeInstalls into the current project.
Run `npx skills use "https://github.com/duthaho/claudekit" --skill "duthaho/claudekit/investigate-root-cause"` 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/duthaho/claudekit" that are relevant to the current task. Run `npx skills add "https://github.com/duthaho/claudekit"` and select the relevant skills, then follow their instructions.