Loading...
Loading...
Found 84 Skills
Systematic methodology for debugging bugs, test failures, and unexpected behavior. Use when encountering any technical issue before proposing fixes. Covers root cause investigation, pattern analysis, hypothesis testing, and fix implementation. Use ESPECIALLY when under time pressure, "just one quick fix" seems obvious, or you've already tried multiple fixes. NOT for exploratory code reading.
Iterative debugging workflow with confidence scoring and strategic log injection. Five phases: investigate, inject logs, propose fix, verify, cleanup. Use when: debugging unexpected behavior, silent errors, intermittent failures, or issues requiring runtime data. Triggers on "debug", "fix bug", "investigate", "trace issue", "add debug logs", "cleanup debug logs".
Use when implementing any feature or bugfix, before writing implementation code
This skill should be used when fixing bugs, implementing features, debugging issues, or making code changes. Ensures understanding of code flow before implementation by: (1) Tracing execution path with specific file:line references, (2) Creating lightweight text diagrams showing class.method() flows, (3) Verifying understanding with user. Prevents wasted effort from assumptions or guessing. Triggers when users request: bug fixes, feature implementations, refactoring, TDD cycles, debugging, code analysis.
Use when a program crashes, a test fails, or code produces wrong results and reading the source isn't enough to see why. Lets you pause execution at any line and inspect the actual runtime state, variable values, types, call stacks, to find what went wrong.
Investigate, fix, postmortem, prevent. Full incident lifecycle from bug report to systemic prevention. Use when: production down, critical bug, incident response, post-incident review. Composes: /investigate, /fix, /postmortem, /codify-learning.
Evidence-based 4-phase root cause analysis: Reproduce, Isolate, Identify, Verify. Use when user reports a bug, tests are failing, code introduced regressions, or production issues need investigation. Use for "debug", "fix bug", "why is this failing", "root cause", or "tests broken". Do NOT use for feature requests, refactoring, or performance optimization without a specific bug symptom.
Use when encountering bugs, test failures, or error logs that need root cause analysis and fix generation
Fix a bug with systematic debugging, TDD, and PR workflow
Full debugging workflow — reproduce the bug with a failing test, perform root cause analysis, then implement a minimal fix.
Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.
Debugging méthodique en 4 phases (reproduce → isolate → fix → verify). Use when investigating a bug, regression, flaky test, or unexpected behavior.