Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- Debug调试复杂或偶现 Bug，需要运行时状态、日志或异步时序证据时使用。优先自行复现，按需使用临时埋点与日志服务器；已有足够证据时直接定位Votes: 0GitHub stars: 6
- DebuggingRoot cause analysis and debugging protocols. Use when encountering errors, test failures, unexpected behavior, stack traces, or when code behaves differently than expected.Votes: 0GitHub stars: 21
- Debugger<!-- AUTO-GENERATED by export-skills.py — DO NOT EDIT --> --- name: debugger description: Debugging specialist for errors, test failures, and unexpected ---Votes: 0GitHub stars: 31
- Systematic DebuggingInvestigate a failure with an unclear cause, repeated unsuccessful fixes, or a cross-component boundary. Use existing reproduction evidence for a localized bug; not a mandatory multi-stage ritual for every edit.Votes: 0GitHub stars: 2,785
- DebugSystematic debugging via logs, health checks, hypothesis-driven investigation. Triggers: debug, error, trace root cause, fix bug, reproduce symptom, investigation.Votes: 0GitHub stars: 177
- DebuggingSystematic debugging workflow for production failures and test regressions.Votes: 0GitHub stars: 24
- DebuggerSystematic debugging specialist focused on root cause analysisVotes: 0GitHub stars: 61
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Implements scientific method for debugging with root cause analysis.Votes: 0GitHub stars: 207
- developer-debugging-methodologyDEBUGGING METHODOLOGY — extracted from roles.json deepPrompt for developerVotes: 0GitHub stars: 8
- DebuggingFind the root cause of a bug instead of guessing at it. Use when the user reports something broken, pastes an error or a stack trace, says this used to work, asks why is this happening, why is this failing, or what is wrong with this. Also use to trace how data flows through a codebase, follow a request end to end, or find where a value is being lost or changed. Also fires on: stack trace, traceback, exception, crash, crashed, segfault, null pointer, undefined, regression, reproduce, bisect, ...Votes: 0GitHub stars: 9
- DebugInvestigate a failure, regression or incorrect result in an integration or application, even before it can be reproduced. Use for diagnosis and repair; follow incident authority for live mitigation.Votes: 0GitHub stars: 950
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Requires root cause investigation first.Votes: 0GitHub stars: 1,760
- DebuggingTo investigate errors, test failures, and unexpected behavior — root cause before fix.Votes: 0GitHub stars: 352
- Debugging调试工具阶梯：print/logging、gdb/lldb/pdb、rr 反向调试、strace/dtruss 与 bpftrace、tcpdump/mitmproxy、 ASan/TSan/MSan/UBSan 与 Valgrind、AI 辅助调试。Use when the user asks to debug a crash, segfault, memory error, flaky test, or race condition. 触发于「帮我调试/排查崩溃/段错误/内存错误/偶发失败」。Votes: 0GitHub stars: 17
- Structured DebugAI DevKit · Guide structured debugging before code changes by clarifying expected behavior, reproducing issues, identifying likely root causes, and agreeing on a fix plan with validation steps. Use when users ask to debug bugs, investigate regressions, triage incidents, diagnose failing behavior, handle failing tests, analyze production incidents, investigate error spikes, or run root cause analysis (RCA).Votes: 0GitHub stars: 1,640
- Debugging WizardParses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting crashes, or performing log analysis, error investigation, or root cause analysis.Votes: 0GitHub stars: 11,720
- Debugging StrategiesTransform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.Votes: 0GitHub stars: 2
- DebuggingSystematic debugging workflow for Replit projectsVotes: 0GitHub stars: 24
- Debugging WizardUse when investigating errors, analyzing stack traces, or finding root causes of unexpected behavior. Invoke for error investigation, troubleshooting, log analysis, root cause analysis.Votes: 0GitHub stars: 8
- Go Systematic DebuggingUse when a bug, flaky test, build failure, hang, deadlock, timeout, or regression has an unknown cause and needs diagnosis or authorized root-cause repair.Votes: 0GitHub stars: 7