🐛Debugging Skills
Browse the best Debugging skills for Claude Code, Codex, Cursor and other AI agents.
989 skills · Page 2 of 42
systematic-debugging
★ 9Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
debugging
★ 8Systematic debugging that identifies root causes rather than treating symptoms. Uses sequential thinking for complex analysis, web search for research, and structured investigation to avoid circular reasoning and whack-a-mole fixes.
systematic-debugging
★ 6Required for any bug, error, test failure, or unexpected behavior. Enforces root cause investigation before fixes through 4-phase framework. Prevents random fix attempts and ensures evidence-based debugging. Auto-invokes on: test failures, errors, crashes, 'not working', performance issues.
bug-debugging
★ 5Systematic bug debugging methodology, root cause analysis, and fix verification. Use when investigating and fixing bugs. (project)
debugging
★ 5Systematic debugging methodology with root cause analysis. Phases: investigate, hypothesize, validate, verify. Capabilities: backward call stack tracing, multi-layer validation, verification protocols, symptom analysis, regression prevention. Actions: debug, investigate, trace, analyze, validate, verify bugs. Keywords: debugging, root cause, bug fix, stack trace, error investigation, test failure, exception handling, breakpoint, logging, reproduce, isolate, regression, call stack, symptom vs cause, hypothesis testing, validation, verification protocol. Use when: encountering bugs, analyzing test failures, tracing unexpected behavior, investigating performance issues, preventing regressions, validating fixes before completion claims.
debugging-strategies
★ 3体系的なデバッグ技術、プロファイリングツール、根本原因分析をマスターし、あらゆるコードベースや技術スタックでバグを効率的に追跡。バグ調査、パフォーマンス問題、予期しない動作の調査時に使用。
bug-fix
★ 3Systematically diagnose and fix bugs by reproducing issues, identifying root causes, implementing fixes, and preventing regressions. Use when debugging errors, fixing issues, or troubleshooting problems.
bugfixforever
★ 2State-of-the-art procedure for fixing bugs in software projects. Use this skill when a bug has been detected or declared by the user, agent, or another skill (not during early-stage work in progress). Enforces a disciplined test-driven approach - understand, reproduce experimentally, write failing tests, fix the code, and clean up.
debugging
★ 2Systematically diagnoses and resolves software bugs using various debugging techniques and tools. Trigger keywords: debug, bug, error, exception, crash, issue, troubleshoot, fix, stack trace.
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 | バグ、テスト失敗、予期しない動作に遭遇した際、修正を提案する前に使用 - 4フェーズフレームワーク（根本原因調査、パターン分析、仮説検証、実装）により、解決策を試す前に理解を確保
debugger
★ 1Advanced debugging specialist for diagnosing and resolving code issues. Use when user encounters bugs, errors, unexpected behavior, or mentions debugging.
debugging
★ 1Use when debugging bugs, test failures, or unexpected behavior. Supports --scientific and --systematic flags for direct methodology selection.
systematic-debugging
★ 1Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
bug-diagnosis
★ 1Use when the user asks to debug, diagnose, fix a bug, troubleshoot errors, investigate issues, or pastes error messages/stack traces. Triggers on keywords like "bug", "error", "fix", "not working", "broken", "debug", "stack trace", "exception", "crash", "issue".
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
systematic-debugging
★ 1Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
debugging
★ 1Comprehensive debugging specialist for errors, test failures, log analysis, and system problems. Use when encountering issues, analyzing error logs, investigating system anomalies, debugging production issues, analyzing stack traces, or identifying root causes. Combines general debugging workflows with error pattern detection and log analysis.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
debugger
Investigate, reproduce, and fix a bug in the codebase. This agent follows a systematic debugging methodology that prioritizes understanding the root cause before implementing fixes. It creates reproducible test cases, validates fixes through TDD principles, and ensures documentation stays current.
debugging-wizard
Systematic debugging expert for all languages and frameworks. Invoke for error investigation, troubleshooting, log analysis, root cause analysis. Keywords: debug, error, bug, traceback, exception, breakpoint.
debugging-strategies
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.
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
debug-phase
Systematic debugging techniques including error classification, root cause analysis (5 Whys), reproduction strategies, and error documentation. Use when debugging errors, investigating failures, analyzing stack traces, fixing bugs, or documenting errors in error-log.md. (project)
debugging
Self-diagnostic debugging - Agent decides diagnostic approach.Auto-activates on "bug", "error", "debug", "不work", "壞掉" keywords.AMP principle: Think > Follow - Agent writes own debug tools.