reproduce-bug

Reproduce GitHub issue bugs by validating reproduction steps and documenting findings.

Updated Nov 11, 2023
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill reproduce-bug-michaelvolz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reproduce-bug
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/reproduce-bug
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill reproduce-bug-michaelvolz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the uncertainty around reproducing and investigating bugs described in GitHub issues by guiding AI through structured analysis, hypothesis formation, reproduction attempts, and reporting.

Core Features & Use Cases

  • Phase-driven workflow: Collect issue metadata, understand symptoms, uncover missing reproduction details, and plan the investigation before touching the codebase.
  • Targeted hypothesis building: Search relevant files, rank plausible root causes, and describe why each hypothesis would yield the reported behavior.
  • Reproduction strategies: Choose between automated tests, browser automation, or manual approaches, log the exact steps taken, and document any environmental requirements or blockers.
  • Investigation reporting: Record findings, cite affected files, and ready a structured summary for the user before asking how they want to proceed.

Quick Start

Use the reproduce-bug skill to analyze the linked GitHub issue and follow the documented phases to confirm the failure.

Frequently Asked Questions about reproduce-bug

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

FAQPage Schema
How do I investigate and reproduce a bug reported in a GitHub issue?

Reproducing a GitHub bug requires harvesting issue metadata, validating reproduction steps, hypothesizing root causes, and attempting test or browser reproductions. This phased investigation confirms the reported behavior and environmental blockers before applying fixes.

What is hypothesis-driven bug investigation and when do I need it?

Hypothesis-driven bug investigation is a method that searches relevant files, ranks plausible root causes, and validates each hypothesis against reported behavior. You need it when issue descriptions lack clear reproduction steps and require structured analysis to confirm failures.

Can I use automated tests and browser automation to reproduce GitHub issues?

Yes, issue reproduction supports choosing between automated tests, browser automation, or manual approaches. The workflow logs exact reproduction steps, documents environmental requirements, and records any blockers encountered during the validation process.

What's the best way to validate missing reproduction steps in a bug report?

The best way to validate missing reproduction steps is through a phase-driven workflow that uncovers missing details, searches relevant files, and ranks plausible root causes. This approach systematically confirms the reported behavior before attempting codebase fixes.

Does bug reproduction work for any repository-level investigation beyond code fixes?

Yes, bug reproduction applies to any repository-level investigation where issue descriptions, environment clues, and reproduction steps must be validated. It harvests issue metadata and summarizes findings regardless of whether immediate code fixes are planned.