Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- DebuggingDebug production failures and test regressions.Votes: 0GitHub stars: 24
- Debugging``` 1. Reproduce → Can you reliably trigger the bug? 2. Isolate → Find the minimal failing case 3. Analyze → Check logs, traces, metrics 4. Hypothesize → Form a theory 5. Test → Verify the theory 6. Fix → Implement the solution 7. Verify → Ensure fix works 8. Prevent → Add test/monitoring ``` ```typescript // Add request ID app.use(async (req, res, next) => { req.id = req.headers['x-request-idVotes: 0GitHub stars: 14
- 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
- DebuggingSystematic four-phase debugging: reproduce, locate, fix, verifyVotes: 0GitHub stars: 188
- 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
- DebugStructured bug diagnosis and fixing workflow that reproduces,Votes: 0GitHub stars: 223
- Debug> Systematic bug investigation: reproduce, isolate, hypothesize, fix, verify, prevent.Votes: 0GitHub stars: 229
- DebuggerUse this agent when you need to diagnose and fix bugs, identify root causes of failures, or analyze error logs and stack traces to resolve issues.Votes: 0GitHub stars: 11
- 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
- Va Debugger\"Use this agent when you need to diagnose and fix bugs, identify root causes of failures, or analyze error logs and stack traces to resolve issues.\".Votes: 0GitHub stars: 25
- DebugDiagnose the current OMC session or repo state using logs, traces, state, and focused reproductionVotes: 0GitHub stars: 39,612
- DebugReproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.Votes: 0GitHub stars: 17
- 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
- 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
- General DebuggerUse when failures are unclear and root-cause analysis is needed quickly.Votes: 0GitHub stars: 3
- Debug HelperSystematic debugging approach for identifying and fixing issuesVotes: 0GitHub stars: 69