🐛Debugging Skills
Browse the best Debugging skills for Claude Code, Codex, Cursor and other AI agents.
989 skills · Page 9 of 42
debug-with-valgrind
★ 2.3kDebug crashes, segfaults, and memory errors using valgrind integration with nextest through pre-configured profiles
observe-before-editing
★ 2.2kObserve Before Editing
handling-rust-errors
★ 1.4kHASH error handling patterns using error-stack crate. Use when working with Result types, Report types, defining custom errors, propagating errors with change_context, adding context with attach, implementing Error trait, or documenting error conditions in Rust code.
debug-hooks
★ 1.3kSystematic hook debugging workflow. Use when hooks aren't firing, producing wrong output, or behaving unexpectedly.
root-cause-tracing
★ 1.1kSystematically trace bugs backward through call stack to find original trigger
clerk-common-errors
★ 939Troubleshoot common Clerk errors and issues.Use when encountering authentication errors, SDK issues,or configuration problems with Clerk.Trigger with phrases like "clerk error", "clerk not working","clerk authentication failed", "clerk issue", "fix clerk".
linear-debug-bundle
★ 939Comprehensive debugging toolkit for Linear integrations.Use when setting up logging, tracing API calls,or building debug utilities for Linear.Trigger with phrases like "debug linear integration", "linear logging","trace linear API", "linear debugging tools", "linear troubleshooting".
deepgram-common-errors
★ 939Diagnose and fix common Deepgram errors and issues.Use when troubleshooting Deepgram API errors, debugging transcription failures,or resolving integration issues.Trigger with phrases like "deepgram error", "deepgram not working","fix deepgram", "deepgram troubleshoot", "transcription failed".
langchain-debug-bundle
★ 939Collect LangChain debug evidence for troubleshooting and support.Use when preparing bug reports, collecting traces,or gathering diagnostic information for complex issues.Trigger with phrases like "langchain debug bundle", "langchain diagnostics","langchain support info", "collect langchain logs", "langchain trace".
langchain-common-errors
★ 939Diagnose and fix common LangChain errors and exceptions.Use when encountering LangChain errors, debugging failures,or troubleshooting integration issues.Trigger with phrases like "langchain error", "langchain exception","debug langchain", "langchain not working", "langchain troubleshoot".
clerk-debug-bundle
★ 939Collect comprehensive debug information for Clerk issues.Use when troubleshooting complex problems, preparing support tickets,or diagnosing intermittent issues.Trigger with phrases like "clerk debug", "clerk diagnostics","clerk support ticket", "clerk troubleshooting".
replit-advanced-troubleshooting
★ 939Apply Replit advanced debugging techniques for hard-to-diagnose issues.Use when standard troubleshooting fails, investigating complex race conditions,or preparing evidence bundles for Replit support escalation.Trigger with phrases like "replit hard bug", "replit mystery error","replit impossible to debug", "difficult replit issue", "replit deep debug".
clay-advanced-troubleshooting
★ 939Apply Clay advanced debugging techniques for hard-to-diagnose issues.Use when standard troubleshooting fails, investigating complex race conditions,or preparing evidence bundles for Clay support escalation.Trigger with phrases like "clay hard bug", "clay mystery error","clay impossible to debug", "difficult clay issue", "clay deep debug".
windsurf-advanced-troubleshooting
★ 920Apply Windsurf advanced debugging techniques for hard-to-diagnose issues.Use when standard troubleshooting fails, investigating complex race conditions,or preparing evidence bundles for Windsurf support escalation.Trigger with phrases like "windsurf hard bug", "windsurf mystery error","windsurf impossible to debug", "difficult windsurf issue", "windsurf deep debug".
rr-debugger
★ 916Deterministic debugging with rr record-replay. Use when debugging crashes, ASAN faults, or when reverse execution is needed. Provides reverse-next, reverse-step, reverse-continue commands and crash trace extraction.
sentry-debug-bundle
★ 878Collect debug information for Sentry support tickets.Use when preparing support requests, debugging complex issues,or gathering diagnostic information.Trigger with phrases like "sentry debug info", "sentry support ticket","gather sentry diagnostics", "sentry debug bundle".
windsurf-debugging-ai
★ 878Use Cascade for intelligent debugging and error analysis. Activate when users mention"debug with ai", "error analysis", "cascade debug", "find bug",or "troubleshoot code". Handles AI-assisted debugging workflows.
debug-like-expert
★ 817Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.
fixing-bugs-systematically
★ 490Diagnose and fix bugs through systematic investigation, root cause analysis, and targeted validation. Use when something is broken, errors occur, performance degrades, or unexpected behavior manifests.
sentry
★ 455Fetch and analyze Sentry issues and search logs directly from the API. Helps agents understand errors, stack traces, logs, and issue context.
debug-lldb
★ 371Capture and analyze thread backtraces with LLDB/GDB to debug hangs, deadlocks, UI freezes, IPC stalls, or high-CPU loops across any language or project. Use when an app becomes unresponsive, switching contexts stalls, or you need thread stacks to locate lock inversion or blocking calls.
problem-analysis
★ 342Invoke IMMEDIATELY for structured problem analysis and solution discovery.
fix-bug
★ 338Guide for fixing bugs in ClaudeBar following Chicago School TDD and rich domain design. Use this skill when:(1) User reports a bug or unexpected behavior(2) Fixing a defect in existing functionality(3) User asks "fix this bug" or "this doesn't work correctly"(4) Correcting behavior that violates the user's mental model
ios-debugger-agent
★ 283Use XcodeBuildMCP to build, run, launch, and debug the current iOS project on a booted simulator. Trigger when asked to run an iOS app, interact with the simulator UI, inspect on-screen state, capture logs/console output, or diagnose runtime behavior using XcodeBuildMCP tools.