ccpm-debugging
Systematic debugging with defense-in-depth approach (symptoms → immediate cause → root cause → systemic issues → prevention). Auto-activates when user mentions "error", "failing", "broken", "debug", "bug", "issue" or when /ccpm:verify runs. Uses Observe → Hypothesize → Test → Confirm → Fix → Verify → Document workflow. Updates Linear with findings and automatically logs blockers that require external fixes. Traces root causes instead of patching symptoms. Integrates with ccpm-code-review to verify fixes pass all gates before marking complete. Suggests binary search for intermittent issues and five-whys analysis for complex problems.
bitcoin-auth-diagnostics
Diagnose and troubleshoot bitcoin-auth token generation and verification issues. This skill should be used when users encounter authentication failures, signature verification errors, or integration problems with the bitcoin-auth library.
ci-failure-analysis
This skill should be used when analyzing failed GitHub Actions CI/CD runs for Breenix kernel development. Use for diagnosing test failures, parsing QEMU logs, identifying kernel panics or faults, understanding timeout issues, and determining root causes of CI failures.
systematic-debugging
This skill should be used when debugging complex kernel issues requiring systematic investigation and documentation. Use for documenting problem analysis, root cause investigation, solution implementation, and evidence collection following Breenix's Problem→Root Cause→Solution→Evidence pattern.
causal-inference-root-cause
Use when investigating why something happened and need to distinguish correlation from causation, identify root causes vs symptoms, test competing hypotheses, control for confounding variables, or design experiments to validate causal claims. Invoke when debugging systems, analyzing failures, researching health outcomes, evaluating policy impacts, or when user mentions root cause, causal chain, confounding, spurious correlation, or asks "why did this really happen?"
postmortem
Use when analyzing failures, outages, incidents, or negative outcomes, conducting blameless postmortems, documenting root causes with 5 Whys or fishbone diagrams, identifying corrective actions with owners and timelines, learning from near-misses, establishing prevention strategies, or when user mentions postmortem, incident review, failure analysis, RCA, lessons learned, or after-action review.
error-debugger
Analyzes errors, searches past solutions in memory, provides immediate fixes with code examples, and saves solutions for future reference. Use when user says "debug this", "fix this error", "why is this failing", or when error messages appear like TypeError, ECONNREFUSED, CORS, 404, 500, etc.
debugging-wizard
Use when investigating errors, analyzing stack traces, or finding root causes of unexpected behavior. Invoke for error investigation, troubleshooting, log analysis, root cause analysis. Keywords: debug, error, bug, traceback, exception, breakpoint.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
debugging
Systematic debugging that identifies root causes rather than treating symptoms. Uses sequential thinking for complex analysis, web search for research, and structured investigation to avoid circular reasoning and whack-a-mole fixes.
log-analyzer
Parse and analyze application logs to identify errors, patterns, and insights.
debugging-with-tools
Use when encountering bugs or test failures - systematic debugging using debuggers, internet research, and agents to find root cause before fixing
root-cause-tracing
Use when errors occur deep in execution - traces bugs backward through call stack to find original trigger, not just symptom
fixing-bugs
Use when encountering a bug - complete workflow from discovery through debugging, bd issue, test-driven fix, verification, and closure
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
container-debugging
Debug Docker containers and containerized applications. Diagnose deployment issues, container lifecycle problems, and resource constraints.
database-monitoring
Monitor database performance and health. Use when setting up monitoring, analyzing metrics, or troubleshooting database issues.
memory-leak-detection
Detect and fix memory leaks using heap snapshots, memory profiling, and leak detection tools. Use when investigating memory growth, OOM errors, or optimizing memory usage.
Page 3 of 5 · 76 results