Loading...
Loading...
Found 26 Skills
Root-cause investigation for bugs, regressions, suspicious runtime behavior, failed automations, and unexpected outcomes.
Use when encountering errors, bugs, unexpected behavior, or any problem requiring systematic debugging with extended thinking for complex multi-layer issues
4-phase root cause debugging: understand bugs before fixing.
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively suggest when the user reports errors, unexpected behavior, or is troubleshooting why something stopped working.
This skill provides expert-level guidance for debugging and fixing bugs in VS Code extensions. Use when investigating runtime errors, fixing memory leaks, resolving WebView issues, debugging activation problems, fixing TypeScript type errors, or troubleshooting extension communication failures. Covers systematic debugging workflows, common bug patterns, root cause analysis, and prevention strategies.
Four-phase debugging framework with root cause tracing - understand the source before proposing fixes. Use when investigating bugs, errors, unexpected behavior, or failed tests.
Helps fail fast on risky implementation steps by prototyping before committing to full code changes. Use during planning or implementation when a step is ambiguous, depends on multiple subsystems or flaky tools, may invalidate the current plan, or when repeated fix attempts suggest a doom loop. Useful both at planning step and during implementation.
Iterative debug loop for Luau/Roblox issues
State-machine driven orchestrator for structured software development. Invoke when user wants to develop features, fix bugs, or refactor code. Triggers: 'build a feature', 'fix this bug', 'implement', 'develop', 'refactor'.
Apply Sherlock Holmes' deductive method to debug code, diagnose system issues, and solve technical puzzles using systematic elimination and logical reasoning
Use when an issue needs deeper analysis than triage — confirming root cause by reading code, verifying file/line references in body are still valid, checking blast radius across the codebase, or proposing a concrete fix direction. One issue per invocation.
Create comprehensive, self-contained task prompts for implementing features or fixing bugs.