🐛Debugging Skills
Browse skills in the Debugging category.
Systematic Debugging
A powerful skill for Claude agents.
React Native Best Practices
A powerful skill for Claude agents.
lovable-setup
Debug and fix Lovable preview/build issues including white screens, module import failures,and monorepo configuration. Use when: (1) Lovable preview shows white/blank screen,(2) "Failed to fetch dynamically imported module" errors, (3) Missing script errors,(4) PostCSS/Tailwind resolution failures, (5) Workspace package resolution errors,(6) 504 Gateway Timeout on dependencies, (7) Setting up monorepo for Lovable deployment.Triggers: "lovable broken", "white screen", "preview not loading", "lovable build failed","dynamic import error", "module not found lovable".
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
gpui-troubleshooting
Common errors and solutions for GPUI development. Use when debugging build errors, runtime panics, borrow checker issues, or unexpected behavior.
debug-helper
调试助手技能。当用户遇到 Bug、错误信息、程序异常、性能问题需要排查，或需要分析日志、定位问题根因时使用此技能。
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
breath-sync-validator
[DEPRECATED] This skill has been consolidated into breathing-sync. Use breathing-sync Mode 2 to validate and debug breathing synchronization.
report-issue
Advanced issue reporter that analyzes codebases, identifies root causes, and creates comprehensive issue documentation. Use this skill when users report bugs, request features, or identify technical debt. This skill investigates and documents without implementing fixes.
python-type-check
Guide for fixing Python strict type checking errors (Pylance/MyPy). Use this skill when resolving unknown type, missing import, or type mismatch errors in Python files. Covers common patterns for TypedDict, generics, casting, and protocol alignment.
debug
Systematic debugging with root cause analysis and hypothesis-driven investigation
problem-solver
Intelligent problem-solving orchestrator that iteratively investigates issues, applies fixes, and verifies success criteria until resolved or exhausted.
fix-application
Apply fixes to entities/components with best practice validation. Searches library docs for simpler patterns, checks for built-in features, validates fixes maintain performance and architectural integrity. Integrates with breath-synchronization skill for breathing-related fixes. Works with parameter tuning, library pattern replacement, and performance optimization.
powershell-utf8-fixer
Detect and fix PowerShell script encoding issues that cause Korean and other non-ASCII characters to display incorrectly on Windows. Use when (1) PowerShell scripts display garbled Korean/non-ASCII text, (2) creating new .ps1 files with non-ASCII content, (3) validating encoding before committing PowerShell scripts, or (4) troubleshooting character display issues in PowerShell output.
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.
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.
context-building
Systematic codebase investigation before addressing issues. Use when you need to build comprehensive understanding of a problem area.
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.
systematic-debugging
Methodical problem-solving workflow for debugging issues. Use when facing bugs, errors, or unexpected behavior that isn't immediately obvious.
error-analysis
This skill should be used when analyzing errors, stack traces, and logs to identify root causes and implement fixes.
python-debugging
Toolkit for AI agents to debug Python code autonomously without IDE support. Use when agent needs to debug code, insert breakpoints programmatically, analyze execution state, test hypotheses, or automate debugging workflows. Supports pdb, ipdb, debugpy with programmatic breakpoint insertion, conditional breakpoints, AST-based breakpoint suggestions, and automated debugging workflows for agents.
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.
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.
codebase-research
Patterns and methods for researching a codebase to understand bug context. Use when investigating how code works, finding related files, or understanding code flow.
ios-debug
Debug and fix iOS/Swift errors. Use when encountering compile errors, runtime errors, crashes, memory leaks, performance issues, SwiftUI preview not working, build failures.
strongs-doctor
Expert assistant for diagnosing and fixing Strong's concordance issues in the Raamattu Nyt project. Use when (1) debugging infinite loops or performance issues with Strong's lookups, (2) validating lexicon data against authoritative sources, (3) checking KJV verses point to correct Strong's numbers, (4) fixing corrupted kjv_strongs_words data, (5) auditing strongs_lexicon entries for format/content issues, or (6) troubleshooting Strong's search functionality. Triggers: strongs issue, lexicon error, infinite loop strongs, strongs validation, kjv strongs, fix strongs, lexicon fix.
problem-solver
Systematic problem-solving workflow for bug fixes and feature implementations. Use when debugging issues, fixing bugs, implementing features, or when the user describes unexpected behavior, errors, or needs a methodical approach to code changes. Ensures reproducible verification and validates solutions are fundamental fixes rather than workarounds.
dev-debug-cpp
C++ debugging for segfaults, memory corruption, threading issues, and linker/ABI problems. Use when encountering crashes (exit code 139/SIGSEGV), memory leaks, data races, undefined behavior, or when debugging native Node.js addons, FFmpeg integrations, or any C++ code that crashes mysteriously.
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.
debugging
Load when encountering errors, exceptions, tracebacks, bugs, or failed operations. Provides systematic troubleshooting methodology for build, runtime, and infrastructure issues.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
debugging
Systematic debugging skill that activates when encountering errors, bugs, or unexpected behavior. Provides structured approach to identifying and fixing issues.
bug-hunter
Copilot 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.
gaussian-particle-designer
3D Gaussian volumetric rendering specialist. Debugs anisotropic stretching, transparency artifacts, cube-like rendering, and particle visual quality. Uses gaussian-analyzer MCP tools for particle structure validation and shader optimization.
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.
error-handler
Design robust error handling with boundaries, logging, and user-friendly messages. Use when implementing error handling, debugging crashes, setting up error tracking, or handling network failures.
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
fix-github-issue
Workflow for analyzing and fixing GitHub issues. Use when given an issue number to investigate and resolve.
tauri-sidecar-troubleshoot
Troubleshoot Tauri sidecar, Rust build, and dev/production mode issues
swift-performance
Optimize SwiftUI and Swift app performance with Instruments profiling, lazy loading, memory management, and view optimization. Use when diagnosing slow UI, fixing memory leaks, optimizing scroll performance, or reducing app launch time.
adk-debugger
Troubleshoot ADK errors and issues. Use when encountering API errors, model overloaded errors, state issues, tool failures, authentication problems, or unexpected agent behavior.
debugging
Systematic debugging workflows for frontend, backend, tests, devops, and web issues. Provides structured approaches to isolate root causes and resolve problems efficiently.
self-directed-debugging
Autonomous development workflow that proactively asks questions, verifies implementation with tools, and auto-fixes linter errors. Use when implementing features to ensure quality through self-driven verification.
debugging-mastery
Systematic debugging methodologies for finding and resolving complex bugs. Use PROACTIVELY when encountering difficult bugs, mysterious failures, or issues that resist simple fixes. MUST BE USED when debugging spans multiple files, involves race conditions, or has eluded initial investigation attempts.
systematic-debugging
This skill should be used when the user asks to "debug this issue", "find the root cause", "investigate the bug", "systematic debugging", "troubleshoot the problem", or needs help with systematic problem-solving and root cause analysis.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
performance-profiling
Advanced iOS performance profiling with Xcode Instruments, real-world optimization case studies, memory debugging with ASAN/TSAN, SwiftUI view optimization, and production performance patterns. Use when user asks about profiling, Instruments, memory leaks, performance optimization, ASAN, TSAN, hangs, stutters, or app performance issues.
use-debug
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
pr-fix
PRの問題修正スキル。レビュー指摘事項とCIエラーを確認し、1つずつ順番に修正してコミットする。「PRの指摘を直して」「CIエラー修正」「レビュー対応」などのリクエスト時に使用。
debug-assistant
调试辅助工具。快速诊断后端、前端和数据库问题。适用于 API 失败、日志分析、服务健康检查等场景。