skills.rest
mukles
muklesCOMMUNITY
Explore all skills by this author →
Website𝕏@mukles_devGitHub

reproduce-bug

Automate bug reproduction and investigation workflows from GitHub issues.

Updated Sep 16, 2025
Search Tags:#workflow#github#issue#investigate#reproduce#hypothesis#bug
One-click install
npx skills add https://github.com/mukles/platejs-markdown-converter --skill reproduce-bug-mukles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reproduce-bug
Source: https://github.com/mukles/platejs-markdown-converter/tree/main/.agents/skills/reproduce-bug
Command: npx skills add https://github.com/mukles/platejs-markdown-converter --skill reproduce-bug-mukles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically reproduce and investigate bugs reported in GitHub issues using a framework-agnostic, hypothesis-driven workflow. It applies across any language, framework, or project type.

Core Features & Use Cases

  • Phase-driven workflow: Understand the issue, hypothesize, reproduce, investigate, and document findings.
  • Cross-project applicability: Works with any language or stack to build reproducible repros and evidence.
  • Structured guidance: Generates hypotheses, reproduction steps, and evidence collection plans from issue reports.

Quick Start

Provide a GitHub issue number or URL to start the reproduction workflow and produce a reproducible bug reproduction plan.

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 reported in a GitHub issue systematically?▼

To reproduce a GitHub bug systematically, follow a hypothesis-driven workflow that includes understanding the issue, formulating hypotheses, reproducing the bug, investigating root causes, and documenting findings with collected evidence.

What is hypothesis-driven bug investigation and when should I use it?▼

Hypothesis-driven bug investigation is a methodical process of forming educated guesses about a defect's cause, testing them through reproduction steps, and analyzing the environment. Use it to systematically trace and verify reported defects.

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

Yes, this bug reproduction workflow is framework-agnostic and applies across any programming language, framework, or project type to help you build reproducible reproduction plans and gather evidence.

What's the best way to document findings when investigating a GitHub issue?▼

The best way to document bug investigation findings is to follow a structured documentation phase that records reproduction steps, environment analysis, tooling commands used, and collected evidence to support the bug report.

How do I start the bug reproduction process from a GitHub issue report?▼

Start the bug reproduction process by providing a GitHub issue number or URL, which triggers a workflow that generates hypotheses, reproduction steps, and an evidence collection plan based on the issue details.

What phases are involved in investigating and reproducing a reported defect?▼

Investigating and reproducing a defect involves five phases: understanding the issue, hypothesizing potential causes, reproducing the bug, investigating the environment and root cause, and documenting the findings.

Related Skills

Explore More Software Engineering Skills→
mediar-aimediar-ai
1.6k

Terminator Issue Reporter

Generate structured GitHub issues for Terminator failures with logs and reproduction steps.

Official
Advanced
qazz92qazz92

bugfix

Automate bug fixing workflows from GitHub issues with reproduction-first verification.

Community
Advanced
timurgaleevtimurgaleev
5

browse

Automate QA flows with a persistent headless Chromium session.

Community
Advanced
ArabelaTsoArabelaTso
142

bug-reproduction-test-generator

Generate executable regression tests from bug reports and stack traces.

Community
Intermediate