πDebugging Skills
Browse the best Debugging skills for Claude Code, Codex, Cursor and other AI agents.
989 skills Β· Page 6 of 42
go-optimization
β
3Performance optimization techniques including profiling, memory management, benchmarking, and runtime tuning. Use when optimizing Go code performance, reducing memory usage, or analyzing bottlenecks.
troubleshooting
β
3Systematic debugging and problem diagnosis using structured troubleshooting methodologiesapplicable to any domain - technical issues, process failures, system problems, or generalobstacles. Use when users report errors, describe malfunctions, encounter unexpected behavior,or need help diagnosing root causes. Triggers include 'debug this,' 'troubleshoot,' 'why isn'tthis working,' 'getting an error,' 'something's wrong with,' 'how do I fix,' or any problemdescription.
systematic-debugging
β
3Systematic debugging framework for any bug, test failure, or unexpected behavior.Use BEFORE proposing fixes. Triggers: "bug", "test failure", "flaky test", "debugging","root cause", "investigate", "why is this failing", "unexpected behavior", "not working","broken", "error", "fix this", "what's wrong".
systematic-debugging
β
2Use 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
cuda
β
2CUDA kernel development, debugging, and performance optimization for Claude Code. Use when writing, debugging, or optimizing CUDA code, GPU kernels, or parallel algorithms. Covers non-interactive profiling with nsys/ncu, debugging with cuda-gdb/compute-sanitizer, binary inspection with cuobjdump, and performance analysis workflows. Triggers on CUDA, GPU programming, kernel optimization, nsys, ncu, cuda-gdb, compute-sanitizer, PTX, GPU profiling, parallel performance.
llm-debugger
β
2Diagnoses LLM output failures including hallucinations, constraint violations, format errors, and reasoning issues. Provides root cause classification, prompt fixes, tool improvements, and new test cases. Use for "debugging AI", "fixing prompts", "quality issues", or "output errors".
systematic-debugging
β
2Use 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
systematic-debugging
β
2Four-phase debugging framework with root cause tracing - understand the source before proposing fixes. Use when investigating bugs, errors, unexpected behavior, or failed tests.
root-cause-tracing
β
1Systematic backward tracing through call chains to find where bugs originate. Triggers on debug, trace, root cause, call stack, error, exception, bug, investigate, find the source, test pollution, flaky test, bisect, why is this failing, where does this come from, track down. Integrates with mcp__zen__debug for hypothesis-driven investigation.
flutter-debugging
β
1Use when encountering any bug, test failure, or unexpected behavior in Flutter - requires systematic investigation before proposing fixes
deno-debugger
β
1Interactive debugger for Deno/TypeScript applications using the V8 Inspector Protocol. This skill should be used when investigating issues in Deno applications, including memory leaks, performance bottlenecks, race conditions, crashes, or any runtime behavior that requires step-by-step debugging, heap analysis, or CPU profiling. Provides CDP client tools, heap/CPU analyzers, and investigation tracking.
website-debug
β
1Frontend website debugging toolkit using Chrome DevTools Protocol with Playwright/WebKit fallbacks. Use this skill when: (1) Debugging CSS, HTML, or JavaScript issues on a webpage, (2) Taking screenshots to verify visual changes, (3) Inspecting DOM structure or console errors, (4) Testing responsive layouts, (5) Extracting selectors for automation, (6) Self-debugging frontend work Claude has created, (7) User says "debug this page", "check my site", "why doesn't this look right", or "fix the frontend". Supports Chrome (primary) and Safari/WebKit (via Playwright). Designed for agent-driven debugging loops.
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
bug-hunter
β
1Copilot agent that assists with bug investigation, root cause analysis, and fix generation for efficient debugging and issue resolutionTrigger terms: bug fix, debug, troubleshoot, root cause analysis, error investigation, fix bug, resolve issue, error analysis, stack traceUse when: User requests involve bug hunter tasks.
systematic-debugging
β
1Use 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
debugging
β
1Troubleshoot and fix bugs systematically. Use when errors occur, tests fail, or unexpected behavior is observed. Covers root cause analysis and debugging strategies.
optimization-performance
β
1Game optimization, performance profiling, multi-platform support, andframe rate optimization for smooth gameplay experiences.
use-debug
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
find-and-fix-bugs
Find, triage, and fix bugs with or without user input. Autonomously scan codebases, produce an issues list, implement a fix, create a fix branch, commit via commit-message, and open a PR with gh.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior in C#/.NET code before proposing fixes; applies to gRPC services, EF Core queries, async operations, and build failures
problem-solver
Intelligent problem-solving orchestrator that iteratively investigates issues, applies fixes, and verifies success criteria until resolved or exhausted.
auto-issue-fixer
Automate the complete GitHub issue lifecycle. Fetches all issues, prioritizes by importance and execution speed, implements fixes using TDD, creates PRs, monitors for reviews, handles feedback autonomously, and notifies when complete. Uses extensive subagent parallelization for context efficiency.
smith-validation
Hypothesis testing, root cause analysis, and debugging techniques. Use when debugging, testing hypotheses, validating solutions, proving correctness, or performing root cause analysis on failures.
debug-specialist
λλ²κΉ , λλ²κ·Έ, λ²κ·Έ, μλ¬, μ€λ₯, λ²κ·Έ μμ - Specialized in identifying root causes of bugs, analyzing error logs, and providing robust fixes. Use this when the user reports an error, unexpected behavior, or needs performance troubleshooting.