Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- Common DebuggingTroubleshoot systematically using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.Votes: 0GitHub stars: 549
- Common DebuggingStop random edits. They destroy causal information and make it unclear which change helped or whether the bug was merely masked. Reset the debugging process without reverting other people’s work: record the symptom, exact reproduction steps, expected versus actual behavior, environment, and current diff. Preserve the state in a branch or patch if needed. Then: 1. Observe the complete error/stack trace, relevant logs, inputs, timing, recent changes, and dependency/configuration versions. 2. Bu...Votes: 0GitHub stars: 549
- Common DebuggingTroubleshoot systematically using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.Votes: 0GitHub stars: 549
- Common DebuggingTwo more untested fixes would be more random debugging. Stop and reopen the root cause instead. 1. Create a minimal deterministic reproduction from the exact failing input and capture the full stack trace, runtime values/types, timing, environment, recent diff, and deployment version. Compare it with the last known-good case. 2. Choose one falsifiable hypothesis from that evidence and run one experiment that changes only its suspected variable—for example, replay the same request with the ups...Votes: 0GitHub stars: 549
- Distributed Debugging Debug TraceYou are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and eVotes: 0GitHub stars: 76
- systematic-debuggerProvides systematic debugging methodology to identify and fix bugs efficiently. Use when user encounters bugs, errors, or unexpected behavior and needs structured debugging approach.Votes: 0GitHub stars: 14
- Common DebuggingTreat this as an environment-specific failure until evidence shows otherwise; do not add a blind fallback first. 1. Observe: capture the production stack trace, source-map position, request/user/context identifiers, input payload, deployment version, and the exact expression whose value is undefined. Compare production logs with the corresponding successful local case, including API responses, feature flags, environment variables, build mode, data shape, and dependency versions. Check recent ...Votes: 0GitHub stars: 549
- 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
- DebugSystematic debugging via logs, health checks, hypothesis-driven investigation. Triggers: debug, error, trace root cause, fix bug, reproduce symptom, investigation.Votes: 0GitHub stars: 177
- 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
- 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
- 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
- Cc DebuggingGuide systematic debugging using scientific method: STABILIZE -> HYPOTHESIZE -> EXPERIMENT -> FIX -> TEST -> SEARCH. Two modes: CHECKER audits debugging approach (outputs status table with violations/warnings), APPLIER guides when stuck (outputs stabilization strategy, hypothesis formation, fix verification). Use when encountering ANY bug, error, test failure, crash, wrong output, flaky behavior, race condition, regression, timeout, hang, or code behavior differing from intent. Triggers on: d...Votes: 0GitHub stars: 369
- DebugRun a structured debugging session to systematically reproduce, isolate, diagnose, and fix software bugs.Votes: 0GitHub stars: 26
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes.Votes: 0GitHub stars: 5