skills.rest
rabbicse
rabbicseCOMMUNITY
Explore all skills by this author →
GitHub

bug-reproduction

Convert vague bug reports into minimal reproductions and failing regression tests.

2|Updated Apr 18, 2021
Search Tags:#debugging#qa#git bisect#bug reproduction#regression test#deterministic repro
One-click install
npx skills add https://github.com/rabbicse/go-projects --skill bug-reproduction-rabbicse
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-reproduction
Source: https://github.com/rabbicse/go-projects/tree/main/projects/movie-ticket-booking/.claude/skills/bug-reproduction
Command: npx skills add https://github.com/rabbicse/go-projects --skill bug-reproduction-rabbicse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns vague bug reports into verified, minimal reproductions so you can fix the real issue instead of guessing at causes.

Core Features & Use Cases

  • Repro extraction: Pulls out the missing details from a thin report, including environment, inputs, frequency, and expected versus actual behavior.
  • Minimize and isolate: Reduces long manual repro paths into the smallest failing case and captures the evidence needed for handoff.
  • Regression defense: Guides you through deterministic repros, git bisect, failing regression tests written before the fix, and fix verification by reverting.
  • Use case: Ideal when a checkout total is wrong sometimes, a bug only appears in one environment, or a defect must be turned into a red test before the code is changed.

Quick Start

Ask the Skill to transform the bug report into a deterministic minimal reproduction and a failing regression test with clear evidence.

Frequently Asked Questions about bug-reproduction

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a vague bug report into a deterministic minimal reproduction?▼

Git bisect investigations work by using the Skill to establish a deterministic reproduction, allowing you to systematically narrow down the specific commit that introduced the regression until the culprit change is identified.

How do I write a failing regression test before fixing a non-reproducible or flaky defect?▼

Writing a failing regression test requires using network stubbing and fixed inputs to eliminate flaky behavior, validating the defect with a red-before-green test, and verifying the fix by reverting the code change to confirm the test fails again.

What is the best way to isolate environment-specific bugs from flaky test failures?▼

Isolating environment-specific bugs involves extracting the exact environment data and inputs, fixing time and randomness, and applying deterministic repro techniques to distinguish genuine environment dependencies from non-reproducible flaky defects.

How do I capture the right evidence for bug reproduction handoff?▼

Capturing evidence for handoff requires minimizing the repro path to the smallest failing case and documenting the deterministic inputs, environment conditions, and the revert-to-verify validation results that confirm the defect.

Does this approach to bug reproduction require network stubbing and fixed randomness?▼

Yes, deterministic bug reproduction requires network stubbing and fixed time and randomness to isolate the defect, ensuring the failing regression test consistently triggers the issue rather than producing flaky or environment-specific results.

Related Skills

Explore More Software Engineering Skills→
sustinbebustinsustinbebustin

feedback-loop

Creates deterministic feedback loops for self-validation across code, UI, and data pipelines.

Community
Advanced
ThalesGroupThalesGroup
19

agilab-testing

Execute targeted AGILAB tests across unit, smoke, and regression suites.

Official
Advanced
ArabelaTsoArabelaTso
142

bisect-aware-instrumentation

Instrument code to produce deterministic pass/fail signals for git bisect runs.

Community
Advanced
cyberelfcyberelf
1

issue-fixer

Guide teams through a repeatable process for identifying and fixing codebase bugs.

Community
Intermediate