bug-report

Translate bug reports into reproducible pipelines with root-cause analysis and PRD artifacts.

17|1|Updated Nov 17, 2024
One-click install
npx skills add https://github.com/mifunedev/orchestra --skill bug-report-mifunedev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-report
Source: https://github.com/mifunedev/orchestra/tree/main/.claude/skills/bug-report
Command: npx skills add https://github.com/mifunedev/orchestra --skill bug-report-mifunedev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end bug reproduction, root-cause analysis, and PRD/Ralph planning by transforming a bug description or GitHub issue into a deterministic pipeline that advances from intake to ready-for-review artifacts.

Core Features & Use Cases

  • Read and interpret a bug report template or issue to extract scope, severity, user stories, and steps to reproduce.
  • Create and manage GitHub issues, branches, and worktrees; reproduce bugs with agent-browser; perform root-cause analysis; generate PRD and Ralph JSON config; commit, push, and update PRs.
  • Archive artifacts and prepare reviewer-friendly results that summarize the fix and testing plan.

Quick Start

Run /bug-report bug=Describe-the-bug-here to start the end-to-end bug-report workflow.

Frequently Asked Questions about bug-report

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

FAQPage Schema
How do I automate bug reproduction from a GitHub issue to a pull request?

Automating bug reproduction from a GitHub issue involves extracting scope and steps, testing with agent-browser, performing root-cause analysis, and generating PRD artifacts. This Skill orchestrates that end-to-end pipeline, pushing commits and wiring results directly to GitHub PRs.

What's the best way to generate PRD and Ralph artifacts for bug remediation?

Generating PRD and Ralph artifacts for bug remediation requires translating root-cause analysis into structured planning documents. This Skill automates that translation after reproducing the bug, creating reviewer-ready summaries and committing them alongside your code changes.

Can I use agent-browser to test bug reproducibility in an automated workflow?

Yes, you can use agent-browser to test bug reproducibility within an automated workflow. This Skill integrates agent-browser directly into its pipeline to validate reported steps, extract severity, and confirm the root cause before generating any remediation artifacts.

How do I manage GitHub worktrees and branches when fixing multiple bugs?

Managing GitHub worktrees and branches for bug fixes is handled automatically by this Skill. It creates isolated worktrees from issue descriptions, performs root-cause analysis in plan mode, and commits reproducible test results directly to the corresponding branch.

Does bug reproduction work without manually writing test steps from scratch?

Bug reproduction works without manually writing test steps by reading and interpreting existing bug report templates or GitHub issues. This Skill extracts user stories, severity, and reproduction steps automatically, then validates them using agent-browser.

What are the limitations of automating root-cause analysis for GitHub issues?

Automating root-cause analysis for GitHub issues depends on the clarity of the initial bug description and the reproducibility of the error within agent-browser. If the issue lacks clear reproduction steps, the generated PRD and Ralph artifacts may require manual refinement.