Loading...
Loading...
Found 57 Skills
Root cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or after multiple fix attempts have failed.
4-phase root cause debugging: understand bugs before fixing.
Use when encountering bugs, unexpected behavior, test failures, or errors during development. Enforces a rigorous 4-phase investigation process that prevents shotgun debugging. Triggers: test failure, runtime error, unexpected behavior, production incident, performance regression.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
Four-phase debugging framework with root cause tracing - understand the source before proposing fixes. Use when investigating bugs, errors, unexpected behavior, or failed tests.
Systematic debugging methodology emphasizing root cause analysis over quick fixes
Use when encountering any bug, test failure, or unexpected behavior. Enforces a strict reproduce-first, root-cause-first, failing-test-first debugging workflow before fixing.
Four-phase debugging framework - root cause investigation, pattern analysis, hypothesis testing, implementation. Ensures understanding before attempting fixes.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Systematic debugging process for Laravel applications - ensures root cause investigation before attempting fixes. Use for any Laravel issue (test failures, bugs, unexpected behavior, performance problems).
Question-only debugging mode that guides users to find root causes themselves through structured questioning. Never gives answers directly. Escalates to systematic-debugging after 12 questions if no progress. Use when: "rubber duck", "help me think through this bug", "debug with me", "walk me through debugging", "socratic debug", "think through this issue"