🐛Debugging Skills
Browse the best Debugging skills for Claude Code, Codex, Cursor and other AI agents.
989 skills · Page 14 of 42
diagnostic-action
★ 12Use when the user asks why something happened, what’s wrong, root cause analysis, debugging, or incident explanation.
performance-auditor
★ 10Audit, optimize, and maintain 60fps performance for emotive-mascot animations. Use when diagnosing performance issues, optimizing particle systems, reducing bundle size, or ensuring smooth animations across devices.
dynamic-debugger
★ 10Interactive debugging via DAP-MCP for multiple languages with natural language commands
root-cause-tracing
★ 9Systematically trace bugs backward through call stack to find original trigger. Use when errors occur deep in execution and you need to trace back to find the original trigger.
mobile-app-debugging
★ 9Mobile app debugging for iOS, Android, cross-platform frameworks. Use for crashes, memory leaks, performance issues, network problems, or encountering Xcode instruments, Android Profiler, React Native debugger, native bridge errors.
smart-bug-fix
★ 8Advanced defect eradication with hypothesis-driven RCA, guarded fixes, and comprehensive validation.
debugging
★ 8Structured debugging protocol for rapid triage, isolation, and fix verification with evidence-backed confidence ceilings.
debugging-websocket-issues
★ 8Use when seeing WebSocket errors like "Invalid frame header", "RSV1 must be clear", or "WS_ERR_UNEXPECTED_RSV_1" - covers multiple WebSocketServer conflicts, compression issues, and raw frame debugging techniques
reverse-engineer-debug
★ 8Rapid triage and debug of binaries or artifacts with static + light dynamic analysis for safe insights.
bugfix
★ 7Systematic bug investigation and fixing workflow with root cause analysis, reproduction tests, and verified fixes. Orchestrates the multi-phase process: gather context, investigate, reproduce, fix, verify.
x-api-debug
★ 6Debug X (Twitter) API issues including stale queryIds, feature mismatches, and partial errors. Use when timeline/bookmarks/replies fail with "Query: Unspecified", "features cannot be null", or HTTP 400 errors.
s-debug
★ 6Diagnose and fix bugs using evidence-based investigation. Requires runtime evidence before fixes—never guess based on code alone. Covers hypothesis-driven debugging, instrumentation logging, Lua errors, taint issues, combat lockdown, and API failures. Triggers: error, bug, debug, fix, crash, taint, nil value, diagnose, hypothesis, runtime, evidence, instrumentation.
dev-swarm-screen-snapshot
★ 6Capture and inspect specific screen regions (e.g., mobile simulators, app windows) using a background streaming process. Use for UI debugging and troubleshooting.
godot-compatibility-checker
★ 6自动检测和修复Godot 3.x与4.x之间的API兼容性问题，基于实际项目经验提供针对性解决方案
generate-fix-suggestions
★ 6Generate fix suggestions based on error patterns and best practices. Use when analyzing failures to get actionable remediation steps.
buck2-build-troubleshoot
★ 6Debugs Buck2 build failures systematically by analyzing error logs, checking common issues (cache, visibility, cycles), and suggesting fixes. Use when builds fail, tests won't run, or Buck2 reports errors.
fix-solution
★ 6Continually test and repair solutions to benchmark problems until they pass. Use when a solution has failing tests. Invoke with /fix-solution <snapshot_path> <problem_name> <checkpoint_index>.
subtest-isolation
★ 6Create minimal subtests to isolate and fix complex bugs. Use when a test fails and the issue is buried in complexity.
recovery-strategies
★ 6Escalation path when stuck on pattern development. Use when encountering TypeScript errors, framework confusion, unexpected behavior, or blocked progress. Five-step recovery: check docs, study examples, strategic investigation (plan mode + subagents), reset and retry, ask user.
strategic-investigation
★ 6Proactive recovery using plan mode and subagents. After 1-2 failed attempts, STOP trying variations. Enter plan mode and launch parallel Explore/Plan agents to find idiomatic solutions instead of spinning wheels.
error-handling-patterns
★ 6Svelte 5 error handling. Use for error boundaries, async await expressions, loading states, and form errors.
vscode-extension-debugger
★ 6This 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.
debugging-stickernest
★ 5Debugging and troubleshooting StickerNest issues. Use when investigating bugs, tracing errors, understanding unexpected behavior, adding debug logging, or when the user says "it's not working", "debug this", or "why is X happening". Covers console patterns, Three.js debugging, React DevTools, network issues, and common gotchas.
error-handling
★ 5Handle errors consistently across frontend and backend. Use when implementing try/catch patterns, error boundaries, API error responses, or error reporting.