skills.rest
apollostreetcompany
apollostreetcompanyCOMMUNITY
Explore all skills by this author →
GitHub

reproduce-bug

Reproduce and investigate bugs from GitHub issues using API access.

Updated Mar 23, 2026
Search Tags:#GitHub#software quality#bug reproduction#code debugging#issue investigation
One-click install
npx skills add https://github.com/apollostreetcompany/codex-compound --skill reproduce-bug-apollostreetcompany
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reproduce-bug
Source: https://github.com/apollostreetcompany/codex-compound/tree/main/plugins/compound-engineering/skills/reproduce-bug
Command: npx skills add https://github.com/apollostreetcompany/codex-compound --skill reproduce-bug-apollostreetcompany

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of systematically reproducing and investigating bugs from GitHub issues, reducing time spent on debugging and increasing efficiency.

Core Features & Use Cases

  • Issue Analysis: Fetches and analyzes bug reports, extracting key details.
  • Code Search: Searches for relevant code paths using native content-search tools.
  • Bug Reproduction: Executes a variety of reproduction strategies, including test-based, browser-based, and manual approaches.
  • Bug Investigation: Provides detailed investigation procedures, including log analysis and code tracing.
  • Documentation: Summarizes findings and presents them to the user for further action.

Quick Start

Reproduce and investigate a bug from GitHub issue #123 by running the reproduce-bug skill with the issue number.

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

To reproduce a bug from a GitHub issue, this Skill fetches the issue details via the GitHub API, analyzes the report, and executes strategies like test-based or browser-based reproduction to confirm the behavior.

What is the best way to investigate the root cause of a GitHub bug?▼

The best way to investigate a GitHub bug root cause is to use a systematic workflow that searches relevant code paths, analyzes logs, and traces code execution to pinpoint the underlying fault.

Do I need GitHub API access to investigate issues with this approach?▼

Yes, you need GitHub API access to fetch issue details and execute commands required for analyzing bug reports and running reproduction strategies.

Can I use this workflow to debug both test-based and browser-based bugs?▼

Yes, you can debug both test-based and browser-based bugs, as the workflow executes a variety of reproduction strategies and provides detailed investigation procedures for different bug types.

How does code search work when investigating a GitHub issue?▼

Code search works by using native content-search tools to find relevant code paths related to the GitHub issue, helping to hypothesize potential causes before executing reproduction steps.

Related Skills

Explore More Software Engineering Skills→
daodaoedudaodaoedu

file-bug-issue

Create a reproducible GitHub issue with reproduction steps and environment details.

Official
Intermediate
a29paula29paul
1

gstack-openclaw-investigate

Enforce root cause investigation before bug fixes in software debugging workflows.

Community
Advanced
RheasilviaRheasilvia

systematic-debugging

Enforce a four-phase debugging methodology to identify root causes.

Community
Advanced
jikig-aijikig-ai
12

reproduce-bug

Reproduce GitHub-reported bugs via logs, code inspection, and Playwright.

Official
Intermediate