🐛Debugging Skills
Browse the best Debugging skills for Claude Code, Codex, Cursor and other AI agents.
989 skills · Page 20 of 42
systematic-debugger
★ 2Systematic debugging skill for complex issues. Use when encountering bugs, test failures, or unexpected behavior. Enforces explore-plan-debug-fix workflow to prevent premature fixes.
automated-code-fixer
★ 2Automated IT helper for detecting and fixing code issues. Use when code fails tests, linting, type-checking, or has security vulnerabilities. Enforces strict quality gates before accepting fixes.
check-concurrency
★ 1Find concurrency issues including race conditions, deadlocks, unsafe shared state, and improper synchronization
problem-solving-expert
★ 1Activate expert reasoning and systematic problem-solving mindset for technical and code-related tasks.
systematic-debugging
★ 1[Debug] Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions. (project)
research-after-failure
★ 1Use after 2 consecutive failed attempts at solving a problem - STOP guessing and research documentation, codebase, and online resources before resuming
dap-protocol-guide
★ 1Comprehensive guide for working with Debug Adapter Protocol in AIDB
rails-error-prevention
★ 1Comprehensive checklist and prevention strategies for common Ruby on Rails errors. Use this skill BEFORE writing any Rails code to prevent ViewComponent template errors, ActiveRecord query mistakes, method exposure issues, N+1 queries, and other common Rails pitfalls. Trigger keywords: errors, bugs, security, validation, prevention, pitfalls, debugging, exceptions, error handling
bug-hunter
★ 1Investigate and fix bugs systematically. Use when debugging issues or tracing errors.
fail-fast-debugging
★ 1Systematic debugging discipline that enforces root cause investigation BEFORE fixes. Triggers on - bug, error, failing, broken, fix, not working, crash, issue, debug, investigate, diagnose, trace, root cause, why is, undefined, null, 500 error, RLS, timeout, infinite loop, exception, stack trace. Integrates with Zen MCP, TodoWrite, and verification-before-completion. Aligns with fail-fast engineering principle.
root-cause-tracing
★ 1Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
error-recovery
★ 1Handle Claude Code errors gracefully - error types, recovery, prevention
debugging-methodology
★ 1Systematic debugging approach with tool recommendations for memory, performance, and system-level issues.
detecting-memory-leaks
★ 1Detect potential memory leaks and analyze memory usage patterns in code. Use when troubleshooting performance issues related to memory growth or identifying leak sources. Trigger with phrases like "detect memory leaks", "analyze memory usage", or "find memory issues".
graphics-troubleshooting
★ 1Debug and fix common issues in Three.js, React Three Fiber, and 3D asset pipelines. Use when encountering visual bugs, performance problems, loading failures, or unexpected behavior. Covers black screens, Z-fighting, memory leaks, shader errors, and physics glitches.
debugging-claude-code
★ 1Troubleshooting guide for Claude Code issues. Use when Claude behaves unexpectedly, tools fail, sessions hang, or you need to diagnose problems. Covers diagnostics, common issues, and recovery procedures.
chrome-debug
★ 1Debug the scoreboard UI in Chrome using DevTools MCP. Inspect page state, console errors, network requests, and interact with elements. Use when debugging UI issues, checking for JS errors, or testing user interactions.
analyzing-logs
★ 1Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage. Use when troubleshooting performance issues or debugging errors. Trigger with phrases like "analyze logs", "find slow requests", or "detect error patterns".
systematic-debugging
★ 1Root cause investigation methodology for bugs and failures. Use when encountering test failures, unexpected behavior, or errors during research or implement phases. Find the cause before attempting fixes.
lang-rust-profiling-eng
★ 1Profile and debug Rust code using valgrind and callgrind with nextest integration. Use when debugging crashes, segfaults, memory errors, analyzing instruction counts, cache behavior, or identifying performance bottlenecks.
code-explorer
★ 1Use when asked to trace existing codepaths or explicitly asked to run the code-explorer subagent.
error-message-explainer
★ 1Interprets Arduino/ESP32/RP2040 compiler errors in plain English for beginners. Use when user shares error messages, compilation failures, upload problems, or asks "what does this error mean". Covers common errors like undefined references, type mismatches, missing libraries, and board-specific issues.
debug-workflow
★ 1Guides developers through scenario test debugging using Ruby debug gem step execution. Provides interactive debugging patterns and test helper context.
circuit-debugger
★ 1Systematic hardware debugging guide for Arduino/ESP32/RP2040 circuits. Use when user reports: circuit not working, components getting hot, no power, intermittent failures, unexpected behavior, sensor not responding, LED not lighting, motor not spinning. Guides through power checks, continuity testing, signal tracing, and component isolation using multimeter techniques.