skills.rest
arozumenko
arozumenkoCOMMUNITY
Explore all skills by this author →
GitHub

reproducing-issues

Convert vague bug reports into repeatable reproduction steps with evidence and a verdict.

18|9|Updated Apr 8, 2026
Search Tags:#quality assurance#debugging#playwright#bug reproduction#evidence capture#root cause analysis handoff
One-click install
npx skills add https://github.com/arozumenko/sdlc-skills --skill reproducing-issues
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reproducing-issues
Source: https://github.com/arozumenko/sdlc-skills/tree/main/skills/reproducing-issues
Command: npx skills add https://github.com/arozumenko/sdlc-skills --skill reproducing-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you convert an unclear or unconfirmed bug report into precise, repeatable reproduction steps with supporting evidence and a clear CONFIRMED / CANNOT-REPRODUCE / PARTIAL verdict.

Core Features & Use Cases

  • Guided reproduction workflow: Intake, environment setup, structured reproduction attempts, and evidence capture.
  • Cross-surface reproduction: UI (Playwright/browser verification), API (curl/script), and logic (minimal repro script), including intermittent scenarios with multiple runs.
  • Handoff-ready outputs: Produces RCA hints without performing fixes, and enforces a confirmation gate before RCA proceeds.
  • Ticket-first documentation: Records everything on the tracker ticket as the source of truth.

Quick Start

Ask your agent to reproduce the bug report on the ticket and conclude with a CONFIRMED, CANNOT-REPRODUCE, or PARTIALLY CONFIRMED verdict with evidence and RCA handoff hints.

Frequently Asked Questions about reproducing-issues

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

FAQPage Schema
How do I reproduce an intermittent bug that only happens sometimes?▼

Bug reproduction for intermittent failures requires multiple timed attempts with detailed environment tracking to capture concrete artifacts like logs and screenshots. This structured process yields a PARTIAL or CONFIRMED verdict by executing repeated reproduction steps until the issue surfaces.

What's the best way to document bug reproduction steps for root cause analysis?▼

Documenting bug reproduction steps for root cause analysis involves capturing environment setup details, screenshots, and API responses as concrete evidence. This process provides RCA hints without fixing code and enforces a confirmation gate before downstream analysis proceeds.

Can I use Playwright to verify and reproduce UI bugs?▼

Playwright is supported for UI bug verification to capture browser-based evidence during reproduction attempts. This cross-surface approach also covers API verification using curl or scripts and logic bugs using minimal repro scripts, ensuring comprehensive evidence capture.

How do I confirm a vague bug report with no clear steps?▼

Confirming a vague bug report involves a guided workflow that transforms unclear descriptions into precise, repeatable reproduction steps. The process outputs a clear CONFIRMED, CANNOT-REPRODUCE, or PARTIALLY CONFIRMED verdict with supporting evidence attached to the tracker ticket.

Why does bug reproduction require a confirmation gate before root cause analysis?▼

A confirmation gate before root cause analysis ensures only verified issues with concrete evidence proceed to RCA. This prevents wasted effort on unconfirmed bugs by requiring a clear CONFIRMED, CANNOT-REPRODUCE, or PARTIAL verdict with documented reproduction steps and artifacts.

What should I do when I cannot reproduce a reported bug?▼

When you cannot reproduce a reported bug, the structured workflow outputs a CANNOT-REPRODUCE verdict after documenting environment setup and failed reproduction attempts. All findings are recorded on the tracker ticket as the source of truth for handoff and future investigation.

Related Skills

Explore More Software Engineering Skills→
simonwjacksonsimonwjackson

se-report-bug

Collect structured bug information and create GitHub issues via the gh CLI.

Community
Advanced
nahisahonahisaho
69

bug-hunter

Diagnose software bugs through investigation, reproduction, and root-cause analysis.

Community
Intermediate
arisngarisng
5

playwright-cli-archived

Automate browser interactions and QA tasks using the Playwright CLI.

Community
Basic
zinohomezinohome
1

test-reporting-triage-skill

Categorize test failures and suggest owners from error messages.

Community
Advanced