skills.rest
All-The-Vibes
All-The-VibesOFFICIAL
Explore all skills by this author →
GitHub

reproduce-bug

Reproduce bugs from GitHub issues and document findings.

50|14|Updated Mar 11, 2026
Search Tags:#debugging#github#bugs#reproduce#issue-tracking#reproduction-workflow
One-click install
npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill reproduce-bug-all-the-vibes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reproduce-bug
Source: https://github.com/All-The-Vibes/ATV-StarterKit/tree/main/.github/skills/reproduce-bug
Command: npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill reproduce-bug-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce bugs from GitHub issues across any project to verify symptoms, reproduce conditions, and gather evidence for debugging.

Core Features & Use Cases

  • Hypothesis-driven reproduction across languages and environments
  • Structured issue analysis, reproduction steps extraction, and evidence collection
  • Use Case: Given a GitHub issue URL or number, reproduce the reported bug and document findings.

Quick Start

Provide a GitHub issue URL or number to begin the reproduction workflow and follow the guided phases.

Frequently Asked Questions about reproduce-bug

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

FAQPage Schema
How do I reproduce a bug from a GitHub issue systematically?▼

To reproduce a bug systematically, provide the GitHub issue URL or number to initiate a structured workflow that extracts reproduction steps, verifies conditions, and collects evidence for debugging.

What is the best way to verify reproduction steps for a reported bug?▼

Verifying reproduction steps requires a phase-driven investigation that analyzes the issue, hypothesizes conditions, and executes the workflow to confirm symptoms and document the findings across diverse environments.

Can I use this workflow to reproduce bugs across any programming language or framework?▼

Yes, the bug reproduction workflow supports diverse languages, frameworks, and environments, enabling hypothesis-driven investigation and evidence collection regardless of the project's specific technology stack.

Do I need repository access to reproduce a bug from an issue?▼

Yes, reproducing a bug from an issue requires access to the repository containing the relevant issue, enabling guided phases from initial understanding to final documentation of the symptoms.

How does hypothesis-driven bug reproduction work in practice?▼

Hypothesis-driven bug reproduction works by systematically analyzing the issue, extracting clear reproduction steps, testing conditions across environments, and gathering concrete evidence to verify the reported symptoms.

What evidence should I collect when reproducing a GitHub issue?▼

When reproducing a GitHub issue, you should collect evidence through a structured workflow that documents verified symptoms, reproduction steps, and environmental conditions to support downstream debugging.

Related Skills

Explore More Software Engineering Skills→
dannys-code-cornerdannys-code-corner
92

create-github-issue

Generate GitHub issue drafts from repository YAML templates and user-provided context.

Official
Intermediate
haingt-devhaingt-dev

fix-issue

Automate GitHub issue resolution from investigation to pull request creation.

Community
Advanced
janjaszczakjanjaszczak

mcp-browser-verify

Validate UI flows and reproduce issues with Playwright browser automation.

Community
Intermediate
d-o-hubd-o-hub
11

rust-code-quality

Review Rust code quality across eight dimensions including async patterns and error handling.

Community
Advanced