debug-reproduction_skill

This skill helps reproduce intermittent bugs and isolate triggers by creating minimal, self-contained tests and validating consistency across environments.

Shell

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill shotaiuchi/dotclaude --skill debug-reproduction

SKILL.md2.2 KB

Overview

This skill helps reproduce and isolate intermittent bugs to find their triggers and produce minimal, reliable test cases. It focuses on systematic isolation of inputs, environment factors, and timing to convert flaky behavior into deterministic steps. Results include a self-contained reproduction case and a confidence-rated diagnosis.

How this skill works

I run a structured investigation: isolate the exact inputs and sequence that trigger the bug, strip unrelated code and configuration to build a minimal reproduction, and test across environments to identify dependencies. I verify consistency by repeating runs, measuring failure rate, and comparing behavior against a known-good baseline. Findings are summarized with confidence ratings and concrete reproduction steps.

When to use it

Intermittent or flaky bugs that are hard to reproduce
When you need a minimal, shareable reproduction case for engineers or CI
To determine whether environmental factors (OS, runtime, hardware) affect the bug
Before filing a clear bug report or creating a patch
When verifying fixes across multiple platforms or versions

Best practices

Start from a clean state and document every step to ensure repeatability
Remove unrelated code and dependencies incrementally to find the minimal trigger
Record environment details: OS, runtime versions, hardware, resource limits, and network conditions
Run the reproduction multiple times and under controlled timing to measure determinism
Compare against a known-good version to confirm the failure reason

Example use cases

Reproduce a race condition that only appears under high load and create a deterministic test harness
Isolate a data-dependent crash by reducing the dataset to a minimal failing record
Verify whether a flaky integration test is caused by external service latency or local timing
Create a concise shell script that reproduces a memory leak for CI regression tests
Confirm that a reported bug is fixed across multiple OS versions before backporting

FAQ

When the minimal case reliably fails in a clean environment and reproduces the original failure reason, it is reproducible enough. Include steps, environment, and failure rate.

What confidence level should I expect for intermittent bugs?

Start with Low or Medium for intermittent behavior until you can reproduce consistently. Raise to High only when repeatable evidence and root-cause indicators are present.