Parallel Debugging
Skill Verified ActiveDebug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows.
Debug complex issues by systematically investigating competing hypotheses in parallel, ensuring thorough root cause analysis and avoiding confirmation bias.
Features
- Hypothesis generation across 6 failure modes
- Standardized evidence collection and citation
- Confidence level assessment for evidence
- Result arbitration protocol for root cause determination
- Validation checklist for proposed fixes
Use Cases
- Debugging bugs with multiple plausible root causes
- Performing systematic root cause analysis
- Organizing parallel investigation workflows
- Avoiding confirmation bias during debugging
Non-Goals
- Executing code or running commands
- Automating the fixing of bugs directly
- Providing generic troubleshooting steps without hypothesis generation
Practical Utility
- info:Usage examplesWhile the skill provides detailed templates for hypotheses and reports, concrete end-to-end examples demonstrating input, invocation, and outcome are not explicitly provided.
Installation
First, add the marketplace
/plugin marketplace add wshobson/agents/plugin install agent-teams@claude-code-workflowsQuality Score
VerifiedTrust Signals
Similar Extensions
Systematic Debugging
100Systematic debugging methodology emphasizing root cause analysis over quick fixes
Node Connect
100Diagnose OpenClaw Android, iOS, or macOS node pairing, QR/setup code, route, auth, and connection failures.
Openclaw Debugging
100Debug OpenClaw model, provider, tool-surface, code-mode, streaming, and live/Crabbox behavior by choosing the right logs, probes, and proof path before changing code.
Troubleshooting
100Uses Chrome DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when list_pages, new_page, or navigate_page fail, or when the server initialization fails.
Root Cause Tracing
99Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior
Query Agent Events
99Bug-investigation tool for the Netdata agent-events ingestion namespace -- triage crashes, panics, fatals across the fleet by downloading events of interest and clustering locally. Covers the three transports (Cloud API and direct agent API are primary; ssh is operator-only), the verified AE_* field map and enum meanings, the dedup model (23h client-side per agent and event signature), the after-the-fact event timing (POST only on agent restart), and the Netdata systemd-journal plugin multi-value filter syntax (FIELD in A, B, C) AND ... Use when investigating crashes / panics / fatals; when grepping for events touching a specific function or file or version; when looking for regressions across versions; when an agent is reported crashing in a way you want to triage. Ships scripts get-events.sh and analyze-events.sh that fetch events with index-friendly filters and compute group-by stats. Defaults to last 24 hours and to the latest stable plus latest 2-3 nightlies.