Does this skill modify code automatically without verification?

No, it follows a strict 'hypothesize before acting' principle, ensuring code changes are only made after a specific theory has been validated with evidence.

Can it help with intermittent bugs or race conditions?

Yes, the methodology includes specific phases for isolation and hypothesis formation designed to handle non-deterministic issues that don't always have obvious error messages.

What is the benefit of the Test Coverage Analysis phase?

It forces an evaluation of why the bug wasn't caught by existing tests, helping developers identify gaps in their CI/CD pipeline and preventing similar regressions in the future.

How does this skill improve debugging speed?

It utilizes parallel subagents to investigate different parts of the codebase or logs simultaneously, significantly reducing the time spent on manual sequential code reading and evidence gathering.

Systematic Debugging

Name: Systematic Debugging
Author: freenet

byfreenet

•

セキュリティとテスト

Implements a structured methodology for identifying, isolating, and resolving complex software bugs using hypothesis-driven investigation.

概要

This skill provides a rigorous framework for Claude to tackle non-trivial technical issues, moving away from 'guess-and-check' fixes toward a scientific debugging process. It guides the AI through explicit hypothesis formation, parallel evidence gathering using specialized subagents, and comprehensive root-cause analysis. By emphasizing test integrity and requiring a 'Why didn't CI catch this?' analysis, it ensures that fixes are robust and prevents future regressions in distributed systems and complex applications where simple errors are rarely the full story.

主な機能

Post-mortem test coverage gap analysis
Hypothesis-driven root cause analysis and ranking
Parallel investigation using codebase-investigator subagents
Structured reproduction and isolation workflows
1 GitHub stars
Anti-pattern prevention to avoid superficial or 'guess-based' fixes

ユースケース

Tracing unexpected behavior in distributed systems or multi-component architectures
Identifying why existing CI/CD pipelines failed to catch a specific production bug
Investigating intermittent test failures or complex race conditions

概要

主な機能

Post-mortem test coverage gap analysis
Hypothesis-driven root cause analysis and ranking
Parallel investigation using codebase-investigator subagents
Structured reproduction and isolation workflows
1 GitHub stars
Anti-pattern prevention to avoid superficial or 'guess-based' fixes

ユースケース

Tracing unexpected behavior in distributed systems or multi-component architectures
Identifying why existing CI/CD pipelines failed to catch a specific production bug
Investigating intermittent test failures or complex race conditions