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
- DebuggingDebuggingVotes: 0GitHub stars: 24
- DebuggingDebug production failures and test regressions.Votes: 0GitHub stars: 24
- DebugDiagnose a concrete failure, regression, crash, hang, flaky test, or incorrect runtime behavior by reproducing it, testing hypotheses, and identifying the evidence-backed root cause. Use when symptoms or failing output exist; do not use for feature implementation without a failure, general code review, or a conceptual explanation.Votes: 0GitHub stars: 20
- Advanced Debugging AssistantSystematic debugging methodology and language-specific debugging commands.Votes: 0GitHub stars: 19
- DebuggingSystematic debugging workflowVotes: 0GitHub stars: 24
- 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: 2
- DebuggingDebugging techniques, tools, and workflows. Use when user asks to "debug this code", "find the bug", "why is this failing", "trace this error", "debug memory leak", "profile this code", "debug network issue", "fix segfault", "debug race condition", "find performance bottleneck", "step through code", "debug async", "debug concurrency", "memory profiling", "CPU profiling", or mentions debugging techniques, error tracing, stack traces, breakpoints, profiling, memory debugging, or troubleshooting...Votes: 0GitHub stars: 207
- 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
- Systematic DebuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesVotes: 0GitHub stars: 2
- 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
- DebuggingDebug failing builds and testsVotes: 0GitHub stars: 24
- 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: 36
- 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
- DebuggingSystematic root-cause debugging with verification. Use for errors, stack traces, broken tests, flaky tests, regressions, or anything not working as expected. For validating bug reports before fixing, use bug-reproduction-validator agent.Votes: 0GitHub stars: 43
- Debugging MasterSystematic debugging methodology - scientific method, hypothesis testing, and root cause analysis that works across all technologiesUse when "bug, debugging, not working, broken, investigate, root cause, why is this happening, figure out, troubleshoot, doesn't work, unexpected behavior, debugging, root-cause, hypothesis, scientific-method, troubleshooting, bug-hunting, investigation, problem-solving" mentioned.Votes: 0GitHub stars: 137
- Debugging WizardUse when isolating a bug or crash from error messages, stack traces, core dumps and logs with a reproduce, isolate, hypothesize, fix and prevent loop in any language. Includes per-language debugger setup, common bug patterns and git bisect strategies; for repairing a whole broken feature use focused-fix.Votes: 0GitHub stars: 21
- 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