Bug Reproduction
Turn a vague bug report into a VERIFIED minimal reproduction and then a failing regression test.
Use Edge to load the skill bug-reproduction from petrkindlmann/qa-skills for my task. If Edge is not set up, read getedge.cc/SKILL.md and ask me first.
2 static scans, 0 counted findings.
Edge checks it again each time your agent loads it.
What it does
- Turn a vague bug report into a VERIFIED minimal reproduction and then a failing regression test, agent-driven end to end.
- Covers extracting the implicit repro from a thin report (env, build, steps, data), the reproduce-minimize-isolate-capture loop, git bisect to find the introducing commit, building a deterministic minimal repro (fixed seeds, frozen time, stubbed network), writing the failing regression test BEFORE the fix (red) and confirming the fix flips it green, and writing repro evidence back into the ticket.
- Distinguishes flaky-not-reproducible from environment-specific.
- Use when: "reproduce this bug," "minimal reproduction," "repro steps," "find the commit that broke it," "git bisect," "make the repro deterministic," "write a failing test for this bug," "regression test for a defect," "can't reproduce this bug." Not for: Classifying/deduplicating/severity-routing existing failures without reproducing them : that is ai-bug-triage.
- Generating tests from specs rather than from a defect : that is ai-test-generation.
- Related: ai-bug-triage, ai-test-generation, test-reliability, systematic-debugging, qa-project-context.
How it works
- 1Copy
Try for free gives you one prompt.
- 2Paste
Paste it into Claude Code, Codex or Cursor.
- 3Ask
Ask for the outcome. Your agent loads Bug Reproduction.
Related skills
Structured bug report from a description, or analyze code for potential bugs. Reproduction steps, severity.
Step-by-step debugging workflow: reproduce the bug, isolate the failing component, trace to root cause, apply a targeted fix, and verify the fix resolves the issue without regressions. Use when you encounter a bug, error
Triage a Playwright bug report by reproducing it from the information in the issue. Use when asked to triage, reproduce, or verify a GitHub issue (a new bug report, or an existing report with a new comment).
Generates a structured Bug Fix Brief (BFB) to document issue corrections. Includes root cause analysis, repro steps, fix options, and fix checklist. Use when user asks to create a BFB, document a bug fix, or generate a b
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not reque
No evidence record yet
No measured run with and without this skill yet, so this page makes no performance claim. 2 static scans, 0 counted findings. Security state at 2026-11-18: reviewed. Static scans check the code, not how well the skill works.
State definitionsSelect the Files tab to load SKILL.md.
Skill details
Security scansReviewed
2 static scans, 0 counted findings. Security state at 2026-11-18: reviewed. Edge checks it again each time your agent loads it.
Edge static checks (Edge-run): edge-static/1.0.2. Scope: Static patterns for remote execution, credentials with network sends, obfuscation, prompt overrides, hidden Unicode, binaries and persistence. Raw findings: not supplied.
Edge committed-secret checks (Edge-run): edge-secrets/1.0.0. Scope: Credentials committed in the skill's files (values never shown). Raw findings: not supplied.
Socket (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
Snyk (skills.sh mirror): Version unavailable. Scope: Not supplied by the mirrored record. Raw findings: not supplied.
- Edge static checks
- Pass · 0 counted findings · 2026-11-18
- Edge committed-secret checks
- Pass · 0 counted findings · 2026-11-18
Creator, source & licencepetrkindlmann
From the petrkindlmann public repository. Edge did not write or edit this skill.
- Repository
- petrkindlmann/qa-skills
- Skill file
- View source at revision
- Revision
- b3bb61bd268b147476252c6ed5a0440c87b97441
- Package hash
- sha256:e62c2a660ecae76a8aa2e6305a9286f4036e17e5832b42587cdbe1520fb82914
- Licence
- MIT
- Description
- Turn a vague bug report into a VERIFIED minimal reproduction and then a failing regression test, agent-driven end to end. Covers extracting the implicit repro from a thin report (env, build, steps, data), the reproduce-minimize-isolate-capture loop, git bisect to find the introducing commit, building a deterministic minimal repro (fixed seeds, frozen time, stubbed network), writing the failing regression test BEFORE the fix (red) and confirming the fix flips it green, and writing repro evidence back into the ticket. Distinguishes flaky-not-reproducible from environment-specific. Use when: "reproduce this bug," "minimal reproduction," "repro steps," "find the commit that broke it," "git bisect," "make the repro deterministic," "write a failing test for this bug," "regression test for a defect," "can't reproduce this bug." Not for: Classifying/deduplicating/severity-routing existing failures without reproducing them : that is ai-bug-triage. Generating tests from specs rather than from a defect : that is ai-test-generation. Related: ai-bug-triage, ai-test-generation, test-reliability, systematic-debugging, qa-project-context.
Quoted from the skill’s own description
Read skill files5 files
5 files, 39.0 KB at revision b3bb61bd268b.
Questions about Bug Reproduction
What does Bug Reproduction do?
Turn a vague bug report into a VERIFIED minimal reproduction and then a failing regression test. Published by petrkindlmann (petrkindlmann/qa-skills).
Is Bug Reproduction safe to use?
Edge security state: Reviewed (2 Edge-run static scans, scanned Nov 18, 2026). The Evidence tab shows the scan.
How do I use Bug Reproduction in Claude Code, Codex or Cursor?
Click Try for free, pick your agent and follow its one step. Edge is free, with no Edge account.