When should I use Layered Tests instead of Test Bombs?

Use Layered Tests when your system follows a pipeline architecture (like a compiler, data processor, or HTTP middleware) and you need to identify exactly which stage is producing incorrect intermediate data.

A Test Bomb is a systematic debugging technique where you list multiple hypotheses for a bug and write a small, independent test for each to quickly eliminate possibilities via pass/fail patterns.

Does this skill help with long-term code quality?

Yes. A key part of the workflow is keeping the generated test bombs and layered tests as permanent regression coverage to ensure the bug never returns.

How do I interpret Test Bomb results if everything fails?

If all tests in a bomb fail, it usually indicates a fundamental setup issue or a broken shared dependency that affects every hypothesis you've listed.

Which programming languages does this skill support?

The skill provides specific implementation patterns and templates for C# (xUnit), TypeScript (Vitest/Jest), Python (Pytest), and Go.

Systematic Debugging

Name: Systematic Debugging
Author: asynkron

byasynkron

•

보안 및 테스팅

Implements structured debugging strategies like test bombs and layered tests to isolate and resolve complex software bugs with unknown root causes.

The Systematic Debugging skill provides a structured framework for tackling 'I don't know why this is broken' scenarios through two primary techniques: Test Bombs and Layered Tests. Test Bombs allow developers to systematically eliminate multiple hypotheses by running small, targeted tests simultaneously, while Layered Tests isolate failures within sequential pipelines like compilers or ETL processes. By providing ready-to-use templates for C#, TypeScript, Python, and Go, this skill transforms chaotic troubleshooting into a repeatable, documented process that results in permanent regression coverage.

주요 기능

01Layered testing strategy for isolating bugs within multi-stage data pipelines.

0230 GitHub stars

03Interpretable pass/fail patterns to quickly identify specific broken components.

04Hypothesis-driven 'Test Bomb' framework for eliminating multiple potential root causes.

05Language-specific templates for C#, TypeScript, Python, and Go testing frameworks.

06Step-by-step guidance for organizing suspected causes into logical test sections.

사용 사례

01Systematically eliminating suspects when a fix attempt fails to resolve an issue.

02Debugging end-to-end test failures where the specific point of failure is opaque.

03Isolating data corruption issues in complex ETL or compiler pipelines.

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add asynkron/asynkron-skills systematic-debug

For use in Claude.ai and ChatGPT

Download Skill