Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- DebugDebug some featureVotes: 0GitHub stars: 33
- DebuggingDiagnose and repair software failures using evidence, reproduction, instrumentation, and regression tests rather than speculative edits.Votes: 0GitHub stars: 2
- DebuggingSystematic root-cause analysis and problem resolution.Votes: 0GitHub stars: 2
- Common DebuggingSystematic troubleshooting using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions. (triggers: debug, fix bug, crash, error, exception, troubleshooting)Votes: 0GitHub stars: 43
- Systematic DebuggingDiagnose failures from runtime evidence before editing code.Votes: 0GitHub stars: 14
- 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
- Debug系统化定位并修复 bug、报错、崩溃或行为异常。当用户贴出报错信息、说"报错了/跑不起来/结果不对/帮我调试"时使用。Votes: 0GitHub stars: 3
- DebuggingSystematic troubleshooting using the Scientific Method. Use when debugging crashes, tracing errors, diagnosing unexpected behavior, or investigating exceptions.Votes: 0GitHub stars: 43
- DebugfixtureVotes: 0GitHub stars: 8
- DebugUse when encountering any bug, test failure, build break, or unexpected behavior — runs a 4-phase systematic debugging process before proposing any fix. Iron Law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST. Produces a `.orchestrator/debug/` artifact the fixer agent must reference.Votes: 0GitHub stars: 53
- 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
- DebuggingRoot-cause analysis for a defect, failing test, crash, regression, or unexplained behavior — "this test fails", "it throws", "it worked yesterday", "why is this null", "intermittent", "wrong output". Enforces reproduce-first and fix-the-cause-not-the-symptom.Votes: 0GitHub stars: 2
- DebuggingTrack down a bug, crash, failing test or "it works locally but not here" — when given an error message, a stack trace, or a report that something behaves wrong. Not for writing new features.Votes: 0GitHub stars: 2
- DebugApply a systematic debugging procedure — reproduce, isolate, fix, verify — instead of guessing at fixesVotes: 0GitHub stars: 3
- Debugging1. Reproduce first, get the exact error. 2. State the hypothesis before fixing. 3. Verify with evidence. 4. Fix the root cause, not the symptom. 5. Add a regression test where possible.Votes: 0GitHub stars: 2
- DebuggingDebug failing builds and testsVotes: 0GitHub stars: 24
- DebugStructured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, \"this works in staging but not prod\", \"something broke after the deploy\", or when behavior diverges from expected and the cause isn't obvious.Votes: 0GitHub stars: 25