reproduce-issue

Reproduce GitHub issue bugs in isolated git worktrees.

5|Updated Jul 25, 2025

Search Tags:#debugging #github #worktree #issue #reproduce #triage #bug

Ready to run

npx skills add https://github.com/tomzx/agents --skill reproduce-issue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: reproduce-issue
Source: https://github.com/tomzx/agents/tree/main/skills/reproduce-issue
Command: npx skills add https://github.com/tomzx/agents --skill reproduce-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reproduce a bug described in a GitHub issue by creating an isolated worktree, analyzing the codebase, and attempting to trigger the reported behavior so you can verify and triage the issue.

Core Features & Use Cases

Create an isolated git worktree for a bug fix while keeping the main repo intact.
Analyze the issue description and the codebase to locate potential failure points.
Attempt to reproduce the bug and report findings back to the issue with clear steps and observations.

Quick Start

Reproduce a reported bug by selecting an issue number and target repository and initiating a reproduction workflow.

Frequently Asked Questions about reproduce-issue

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

FAQPage Schema

How do I reproduce a bug from a GitHub issue without affecting my main repository?▼

You can reproduce a bug from a GitHub issue using an isolated git worktree. This approach keeps your main repository intact while analyzing the codebase and attempting to trigger the reported failure in a dedicated, safe environment.

What is the best way to isolate a codebase when triaging reported bugs?▼

Using git worktree is an effective way to isolate a codebase for bug triage. It creates a dedicated directory linked to the repository, allowing you to attempt deterministic reproduction and analyze potential failure points without modifying your primary working directory.

Do I need gh and git worktree installed to reproduce issues with this approach?▼

Yes, you need both gh and git worktree installed to reproduce issues with this approach. You also need access to the target GitHub repository and the specific issue number to initiate the reproduction workflow and analyze the codebase.

How to analyze a GitHub issue and locate potential failure points in the code?▼

To analyze a GitHub issue, you create a worktree and parse the issue description to locate potential failure points in the code. The skill attempts to trigger the reported behavior, enabling structured observation and clear reporting of findings back to the issue.

Can I use this workflow to reproduce bugs across different GitHub repositories?▼

Yes, you can use this workflow to reproduce bugs across different GitHub repositories. The skill is applicable to issues across repositories, requiring only the target repository access and the specific issue number to start the reproduction process.

Why should I use a worktree for debugging instead of switching branches in my main repo?▼

You should use a worktree for debugging to keep your main repository intact. Worktrees provide an isolated environment for deterministic reproduction attempts, preventing potential conflicts with your current work while you analyze the codebase and trigger failures.