πDebugging Skills
Browse the best Debugging skills for Claude Code, Codex, Cursor and other AI agents.
989 skills Β· Page 7 of 42
bug-coordinator
Orchestrates the complete bug-fixing workflow from Jira ticket to implementation. Use when starting to fix a bug, managing the bug-fixing pipeline, or checking workflow progress.
fix-github-issue
Investigate and fix a GitHub issue using gh, then validate with tests and create a PR. Use when a user references a GitHub issue number or asks to fix an issue.
systematic-debugging
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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
systematic-debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
systematic-debugging
Use for bugs, test failures, or unexpected behavior needing root cause
bug-interview
Deeply interviews the user about a bug before investigating or fixing it. Use this when the user says "interview me about [bug]", "I have a bug to report", "let's work on this bug", "found a bug", "there's a bug", or describes a bug they encountered. Asks probing questions about reproduction steps, environment, patterns, impact, and context that help isolate the root cause. Continues until the bug is well-understood, then writes a detailed investigation/fix plan.
chrome-devtools
Chrome DevTools MCP for interactive debugging and development. Use for CSS inspection, network debugging, console access, performance profiling, and real-time development iteration.
systematic-debugging
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-workflow
λλ²κΉ μ€ν¨ μ μλ νΈλ¦¬κ±°λλ 체κ³μ λ¬Έμ ν΄κ²° μν¬νλ‘μ°. DEBUGGING_STRATEGY.md κΈ°λ° Phase 0-3 λλ²κΉ νλ‘μΈμ€ μλν.
full-stack-debugger
This skill should be used when debugging full-stack issues that span UI, backend, and database layers. It provides a systematic workflow to detect errors, analyze root causes, apply fixes iteratively, and verify solutions through automated server restarts and browser-based testing. Ideal for scenarios like failing schedulers, import errors, database issues, or API payload problems where issues originate in backend code but manifest in the UI.
infrastructure-debugging
Troubleshooting dependencies, installations, environment issues, and platform-specific problems. Use when facing npm/pip/package errors, installation failures, environment setup issues, or platform compatibility problems.
multi-ai-consultant
Consult external AIs (Gemini 2.5 Pro, OpenAI Codex, fresh Claude) for second opinions when stuck on bugs or making architectural decisions. Use when: debugging attempts have failed, making significant architectural choices, security concerns, or need fresh perspective. Automatically suggests consultation after one failed attempt. Provides synthesis comparing multiple AI perspectives with web research, thinking mode, and repo-aware analysis.
issue-resolution
GitHub μ΄μ ν΄κ²° μν¬νλ‘μ°. λΆμ β ꡬν β κ²μ¦ μλν.
debug-mode
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.
error-learner
**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
Use when user encounters errors or bugs in their automation tool. Guides through systematic debugging: reproduce error β collect info β analyze root cause β fix β verify. Triggered by "/debug" command or error reports.
backend-python-performance
Profile and optimize Python backend code using cProfile, memory profilers, and performance best practices. Use when debugging slow FastAPI code, optimizing bottlenecks, or improving application performance.
error-debugger
Analyzes errors, searches past solutions in memory, provides immediate fixes with code examples, and saves solutions for future reference. Use when user says "debug this", "fix this error", "why is this failing", or when error messages appear like TypeError, ECONNREFUSED, CORS, 404, 500, etc.
bash-script-helper
Expert helper for bash scripting, debugging, and best practices
ossissue-analysis
Phase 2 of OSS contribution - Deep analysis combining issue requirements with codebase exploration. Extracts requirements, explores code structure, identifies exact code locations to fix, traces execution paths, and maps code-level changes needed. Use when starting work on selected issue.
resolving-type-errors
Resolve all TypeScript errors using root cause analysis, targeted fixes, and mandatory validation
systematic-debugging
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
python-performance
Use when Python code runs slowly, needs profiling, requires async/await patterns, or needs concurrent execution - covers profiling tools, optimization patterns, and asyncio; measure before optimizing (plugin:python@dot-claude)