skills.rest
jaydubya818
jaydubya818COMMUNITY
Explore all skills by this author →
GitHub

reproduce-bug

Reproduce and investigate GitHub issue bugs with a hypothesis-driven workflow.

Updated Mar 26, 2026
Search Tags:#workflow#debugging#investigation#reproduce#root-cause#bug#github-issues
One-click install
npx skills add https://github.com/jaydubya818/New_baseline --skill reproduce-bug-jaydubya818
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reproduce-bug
Source: https://github.com/jaydubya818/New_baseline/tree/main/skills/compound-engineering/plugins/compound-engineering/skills/reproduce-bug
Command: npx skills add https://github.com/jaydubya818/New_baseline --skill reproduce-bug-jaydubya818

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce and investigate bugs described in GitHub issues using a repeatable, hypothesis-driven workflow that reduces debugging time and miscommunication.

Core Features & Use Cases

  • Phase-based issue understanding: fetch, parse, and structure bug reports from GitHub.
  • Hypothesis-driven repro: generate targeted reproduction steps and gather evidence across languages and environments.
  • Report generation: compile root-cause analysis, reproduction steps, evidence, and suggested fixes into a sharable bug report.

Quick Start

Provide the GitHub issue number or URL to initiate the reproduction workflow.

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?▼

To reproduce a bug from a GitHub issue, provide the issue URL or number along with symptom descriptions and environment details. This triggers a structured workflow that fetches and parses the report to generate targeted reproduction steps across any programming language or project environment.

What is a hypothesis-driven workflow for debugging?▼

A hypothesis-driven debugging workflow systematically investigates bugs by applying structured phases for understanding, hypothesizing, reproducing, and investigating issues. It reduces debugging time and miscommunication by generating targeted reproduction steps and gathering concrete evidence before reporting findings.

How do I find the root cause of a bug across different environments?▼

Finding a bug's root cause across different environments involves structured issue understanding and hypothesis-driven reproduction. By gathering evidence based on reported symptoms and environment details, the investigation phase isolates the underlying fault and generates recommended fixes.

Can I investigate bugs reported in any programming language project?▼

Yes, you can investigate bugs reported in any programming language project. The reproduction workflow applies to any repository issue provided you supply the GitHub issue URL or number alongside the symptom descriptions and environment details.

What is the best way to report GitHub bug investigation findings?▼

The best way to report GitHub bug investigation findings is to compile a structured report containing root-cause analysis, reproduction steps, gathered evidence, and suggested fixes. This sharable format reduces miscommunication and provides actionable recommendations.

Related Skills

Explore More Software Engineering Skills→
kartikkabadikartikkabadi

qa

Converts conversational bug reports into GitHub issues with reproduction steps.

Community
Advanced
benmatselbybenmatselby
68

bms:github-issue-analyzer

Fetch GitHub issue details and generate a root-cause analysis with file references.

Community
Advanced
shekerkammashekerkamma

investigate

Systematically debugs software errors by tracing root causes before implementing fixes.

Community
Advanced
jlawsjlaws
2

cmd-workflow-team-investigate

Debug complex software bugs through sequential hypothesis testing and root-cause reporting.

Community
Advanced