Mmcp.market

parallel-debugging skill

by wshobson·wshobson/agents·40k stars·MIT

Debug 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.

A100/100content scan

Is the parallel-debugging skill safe?

Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.

No findings.

Install the parallel-debugging skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/wshobson/agents.git /tmp/agents
mkdir -p ~/.claude/skills
cp -r /tmp/agents/plugins/agent-teams/skills/parallel-debugging ~/.claude/skills/parallel-debugging
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Parallel Debugging

Framework for debugging complex issues using the Analysis of Competing Hypotheses (ACH) methodology with parallel agent investigation.

When to Use This Skill

  • Bug has multiple plausible root causes
  • Initial debugging attempts haven't identified the issue
  • Issue spans multiple modules or components
  • Need systematic root cause analysis with evidence
  • Want to avoid confirmation bias in debugging

Hypothesis Generation Framework

Generate hypotheses across 6 failure mode categories:

1. Logic Error

  • Incorrect conditional logic (wrong operator, missing case)
  • Off-by-one errors in loops or array access
  • Missing edge case handling
  • Incorrect algorithm implementation

2. Data Issue

  • Invalid or unexpected input data
  • Type mismatch or coercion error
  • Null/undefined/None where value expected
  • Encoding or serialization problem
  • Data truncation or overflow

3. State Problem

  • Race condition between concurrent operations
  • Stale cache returning outdated data
  • Incorrect initialization or default values
  • Unintended mutation of shared state
  • State machine transition error

4. Integration Failure

  • API contract violation (request/response mismatch)
  • Version incompatibility between components
  • Configuration mismatch between environments
  • Missing or incorrect environment variables
  • Network timeout or connection failure

5. Resource Issue

  • Memory leak causing gradual degradation
  • Connection pool exhaustion
  • File descriptor or handle leak
  • Disk space or quota exceeded
  • CPU saturation from inefficient processing

6. Environment

  • Missing runtime dependency
  • Wrong library or framework version
  • Platform-specific behavior difference
  • Permission or access control issue
  • Timezone or locale-related behavior

Evidence Collection Standards

What Constitutes Evidence

Citation Format

Always cite evidence with file:line references:

**Evidence**: The validation function at `src/validators/user.ts:87`
does not check for empty strings, only null/undefined. This allows
empty email addresses to pass validation.

Confidence Levels

Result Arbitration Protocol

After all investigators report:

Step 1: Categorize Results

  • Confirmed: High confidence, strong evidence, clear causal chain
  • Plausible: Medium confidence, some evidence, reasonable causal chain
  • Falsified: Evidence contradicts the hypothesis
  • Inconclusive: Insufficient evidence to confirm or falsify

Step 2: Compare Confirmed Hypotheses

If multiple hypotheses are confirmed, rank by:

  1. Confidence level
  2. Number of supporting evidence pieces
  3. Strength of causal chain
  4. Absence of contradicting evidence

Step 3: Determine Root Cause

  • If one hypothesis clearly dominates: declare as root cause
  • If multiple hypotheses are equally likely: may be compound issue (multiple contributing causes)
  • If no hypotheses confirmed: generate new hypotheses based on evidence gathered

Step 4: Validate Fix

Before declaring the bug fixed:

  • [ ] Fix addresses the identified root cause
  • [ ] Fix doesn't introduce new issues
  • [ ] Original reproduction case no longer fails
  • [ ] Related edge cases are covered
  • [ ] Relevant tests are added or updated

More skills from wshobson/agents

  • Aairflow-dag-patternsBuild production Apache Airflow DAGs with best practices for operators, sensors, testing, and deployment. Use when creating data pipelines, orchestrating workflows, or scheduling batch jobs.
  • Aangular-migrationMigrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code.
  • Aanti-reversing-techniquesUnderstand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use this skill when analyzing malware evasion techniques, when implementing anti-debugging protections for CTF challenges, when reverse engineering packed binaries, or when building security research tools that need to detect virtualized environments.
  • Aapi-design-principlesMaster REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.
  • Aarchitecture-decision-recordsWrite and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.
  • Aarchitecture-patternsImplement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or when debugging dependency cycles between application layers.
  • Aasync-python-patternsMaster Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.
  • Aauth-implementation-patternsMaster authentication and authorization patterns including JWT, OAuth2, session management, and RBAC to build secure, scalable access control systems. Use when implementing auth systems, securing APIs, or debugging security issues.
  • Aavoid-ai-writingAudit and rewrite prose so it stops reading as machine-generated. Use this skill when asked to remove AI-isms, clean up AI writing, edit a draft for AI tells, audit a README, changelog, release note, PR description, or blog post for machine-sounding prose, or make text sound less like AI. Supports a detect-only mode, a rewrite mode, and an edit-in-place mode, with optional voice and context profiles.
  • Abacktesting-frameworksBuild robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strategies, or building backtesting infrastructure.
  • Abazel-build-optimizationOptimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
  • Abefore-you-buildPre-build product and feature risk review for founders, product managers, and AI-assisted builders. Use this skill when the user is about to build a landing page, MVP, SaaS product, internal tool, agent workflow, or major feature and needs to check demand, positioning, monetization, retention, trust, distribution, and adoption risk before implementation starts.

All agent skills → · MCP servers