🐛Debugging Skills
Browse the best Debugging skills for Claude Code, Codex, Cursor and other AI agents.
989 skills · Page 19 of 42
systematic-debugging
★ 24-phase debugging process (Observe, Hypothesize, Test, Fix) for complex issues. Use when debugging fails, investigating flaky tests, tracking root causes, or facing mysterious bugs.
chain-of-thought
★ 2INVOKE for debugging and step-by-step problem solving. Produces visible reasoning trace with each step shown. Use when tracing logic, explaining reasoning, or debugging issues. Triggers: debugging, tracing execution, explaining how something works, step-by-step problems.
priority-issue-resolution
★ 2Autonomous issue resolution workflow for processing priority issues in polymarket-insider-tracker. Covers claiming, investigation, worktree-based fixes, PR shepherding, and CI monitoring. Activates on "fix issues", "resolve bugs", "claim issue", "priority queue", "issue triage", or "autonomous resolution".
code-archaeology
★ 2Systematic techniques for reading and understanding unfamiliar legacy code without documentation
odoo-debugger
★ 2Analyzes and resolves Odoo 16.0 issues including SVL linking problems, queue job failures, view errors, and business logic bugs. This skill should be used when the user reports problems such as "Debug this SVL linking issue" or "Queue job is failing" or "View not showing correctly" or "Figure out why this vendor bill isn't linking to stock moves".
root-cause-tracing
★ 2Use 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
debugging-memory
★ 2This skill should be used when the user asks to "debug this", "fix this bug", "why is this failing", "investigate error", "getting an error", "exception thrown", "crash", "not working", "what's causing this", "root cause", "diagnose this issue", or describes any software bug or error. Also activates when spawning subagents for debugging tasks, using Task tool for bug investigation, or coordinating multiple agents on a debugging problem. Provides memory-first debugging workflow that checks past incidents before investigating.
koan-debugging
★ 2Framework-specific troubleshooting, boot report analysis, common error patterns
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
revising-findings
★ 2Implement findings from verification reports with scope-based parallel workflow
debug
★ 2Expert debugging methodology. Triggers on debug, investigate, fix bug, troubleshoot.
root-cause-tracing
★ 2Systematically trace bugs backward through call stack to find original trigger
log-review
★ 2Inspect error logs quickly; use when log snippets or stack traces are mentioned.
fullstory-logging
★ 2Comprehensive guide for implementing Fullstory's Logging API (log method) for web applications. Teaches proper log level usage, message formatting, and capturing application logs in session replay. Includes detailed good/bad examples for error tracking, debugging, and operational monitoring to help developers add contextual log messages to Fullstory sessions.
script-bugfix
★ 2Debug and fix complex scripts by isolating side effects, extracting core logic into a controlled environment, validating behavior there, then reintegrating with minimal changes. Use this when scripts lack unit tests and are hard to reason about due to IO, environment, or orchestration complexity.
code-cleanup
★ 2Delegate repetitive tasks to specialized agent to preserve context. Use when user asks to fix linting errors, fix diagnostics, rename variables across files, update imports, fix formatting issues, or perform other mechanical bulk changes across multiple files.
tmux
★ 2Remote control tmux sessions for interactive CLIs (python, gdb, git add -p, etc.) by sending keystrokes and scraping pane output. Use when debugging applications, running interactive REPLs (Python, gdb, ipdb, psql, mysql, node), automating terminal workflows, interactive git commands (git add -p, git stash -p, git rebase -i), or when user mentions tmux, debugging, or interactive shells.
apple-tv-troubleshooter
★ 2Expert troubleshooting for Apple TV (tvOS) React Native development. Use when users have issues with Siri Remote, focus management, TVEventHandler, TVFocusGuideView, ScrollView not scrolling, tvOS-specific problems, parallax animations, or tvOS vs Android TV differences.
unity-performance
★ 2Optimize Unity game performance through profiling, draw call reduction, and resource management. Masters batching, LOD, occlusion culling, and mobile optimization. Use for performance bottlenecks, frame rate issues, or optimization strategies.
swift-6-migration
★ 2Use when encountering Swift 6 concurrency errors, Sendable conformance warnings, actor isolation issues, "global variable is not concurrency-safe" errors, or migrating codebases to Swift 6 language mode
react-performance
★ 2React Native performance optimization guide. Use when working on performance issues, optimizing renders, improving startup time, debugging memory leaks, optimizing lists/animations, or analyzing bundle size. Covers profiling, memoization, React Compiler, Concurrent React, state patterns, FlatList optimization, Reanimated, native threading, and bundle optimization.
instruments-profiling
★ 2Use when profiling native macOS or iOS apps with Instruments/xctrace. Covers correct binary selection, CLI arguments, exports, and common gotchas.
codegen-bug-fix
★ 2Fix bugs using TDD starting from README + Issue (following codegen-test), aligning with existing implementation conventions, and leveraging Serena MCP semantic search/editing to implement changes with high performance and race-safety in mind.
memory-management-optimization
★ 2Debug memory leaks, profile memory usage, optimize allocations. Use when heap grows unexpectedly, OOM errors occur, allocation performance matters, profiling shows memory bottleneck, Valgrind/ASAN reports issues, or Python objects not being collected. Covers C++ (Valgrind, ASAN, RAII), Python (tracemalloc, objgraph), and general patterns.