debug-ops
SolidSystematic debugging methodology, language-specific debuggers, and common scenario playbooks. Use for: debug, debugging, bug, crash, hang, memory leak, race condition, deadlock, bisect, reproduce, root cause, breakpoint, profiling, performance issue, segfault, stack trace, core dump.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- 0xDarkMatter
- Repository
- 0xDarkMatter/claude-mods
- Created
- 10 months ago
- Last Updated
- 1 weeks ago
- Language
- Shell
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
debug
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
ops-debugging
Symptom-indexed playbook for deployment/environment debugging — SSH tunnels, reverse proxies, TLS, container lifecycle, secret rotation, and real-time API integration failures that "work locally, break deployed." Every entry traces to a real diagnosed incident (probe -> resolution), stated at the failure-class level so it generalizes across projects. Use when a deploy-only symptom, a "works here but not there" report, or an environment-boundary failure needs the fastest-discriminating probe, not generic debugging methodology (that lives in /ms.fix's Hard-Bug Discipline).
systematic-debugging
Use when encountering a bug, test failure, or unexpected behavior, before proposing fixes