Best Debugging Claude Skills & MCP Tools (2026)

debug-mode

from Remedy92

Autonomous debugging workflow mirroring Cursor IDE's debug mode. Triggers on "debug mode", "help me debug", error messages, stack traces, or debugging loops. Generates 5-7 hypotheses, narrows to top 2, adds strategic logs with [DEBUG:] prefix, collects logs via local server, analyzes, fixes, and cleans up.

rust-code-debugger

from UtakataKyosui

Diagnoses and fixes Rust compile errors, borrow-checker issues, runtime panics, and logic bugs with clear explanations and idiomatic solutions.

debugging-auto

from timequity

Hidden automatic debugging when something breaks - user sees simple question or "fixing..." not stack traces or technical errors

find-and-fix-bugs

from graysurf

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.

developer-detective

from involvex

⚡ PRIMARY TOOL for: 'how does X work', 'find implementation of', 'trace data flow', 'where is X defined', 'audit integrations', 'find all usages'. Uses claudemem v0.3.0 AST with callers/callees analysis. GREP/FIND/GLOB ARE FORBIDDEN.

rca-analysis

from mabrax

Perform Root Cause Analysis using a multi-agent swarm approach. Use when investigating bugs, failures, performance issues, or any problem requiring systematic diagnosis. Triggers on requests like "why is X failing", "debug this issue", "find the root cause", "investigate this problem", or explicit RCA requests.

error-learner

from coopeverything

**AUTO-TRIGGER:** Invoked by yolo1 skill after every commit to analyze session errors.Analyzes the current session for error patterns, researches solutions, and either:1. Updates knowledge files immediately (if pattern repeats 2+ times in session)2. Stores findings for cross-session tracking (if one-off error)On subsequent invocations, checks for cross-session patterns and promotes findings to knowledge.

debug

from thoreinstein

Guide systematic debugging through hypothesis generation and verification

systematic-debugging

from jrc1883

Four-phase debugging: root cause → patterns → hypothesis → implement. For complex bugs, test failures, multi-component issues. NOT for obvious syntax errors.

performance-optimization

from dseirz-rgb

性能优化技能：诊断和优化 React 前端、API 响应、数据库查询性能。Use when: 页面加载慢、组件渲染卡顿、API 响应超时、数据库查询慢。Triggers: "性能", "优化", "慢", "卡顿", "加载", "响应时间", "渲染"

debugger-detective

from tianzecn

⚡ PRIMARY TOOL for: 'why is X broken', 'find bug source', 'root cause analysis', 'trace error', 'debug issue', 'find where X fails'. Uses claudemem v0.3.0 AST with context command for call chain analysis. GREP/FIND/GLOB ARE FORBIDDEN.

systematic-debugging

from penne-0505

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

debugging-process

from kokuyouwind

Provides systematic debugging methodology for thorough root cause analysis with evidence-based investigation. Use this skill when investigating code, analyzing bugs, tracing errors, or understanding unexpected behavior.

forensic-surgeon

from agentydragon

Deep forensic debugging that never stops until root cause is found or visibility limit is proven. Use when user wants to understand exactly why something is broken, not work around it. Activates on "why is this happening", "dig deeper", "don't work around it", "I want to understand", "find the root cause", "this seems suspicious", or when a problem suggests deeper breakage.

grey-haven-performance-optimization

from greyhaven-ai★ 15

Comprehensive performance analysis and optimization for algorithms (O(n²)→O(n)), databases (N+1 queries, indexes), React (memoization, virtual lists), bundles (code splitting), API caching, and memory leaks. 85%+ improvement rate. Use when application is slow, response times exceed SLA, high CPU/memory usage, performance budgets needed, or when user mentions 'performance', 'slow', 'optimization', 'bottleneck', 'speed up', 'latency', 'memory leak', or 'performance tuning'.

Systematic Debugging

from obra★ 35.6k

A powerful skill for Claude agents.

python-performance-optimization

from wshobson★ 24.2k

Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.

debugging-strategies

from wshobson★ 24.2k

Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.

try-fix

from dotnet★ 23.1k

Proposes ONE independent fix approach, applies it, runs tests, records result with failure analysis in state file, then reverts. Reads prior attempts to learn from failures. Returns exhausted=true when no more ideas. Max 5 attempts per session.

debug-cuda-crash

from flashinfer-ai★ 4.4k

Tutorial for debugging CUDA crashes using API logging

systematic-debugging

from ChrisWiles★ 3.8k

Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.

error-handling

from EpicenterHQ★ 3.8k

Error handling patterns using wellcrafted trySync and tryAsync. Use when writing error handling code, using try-catch blocks, or working with Result types and graceful error recovery.

profiling

from facet-rs★ 2.3k

Profile code performance using callgrind and valgrind with nextest integration for analyzing instruction counts, cache behavior, and identifying bottlenecks

reproduce-reduce-regress

from facet-rs★ 2.3k

Systematic workflow for debugging by reproducing bugs with real data, reducing test cases to minimal examples, and adding regression tests

← Back to All Skills