bug-to-pr

Automate end-to-end bug-to-PR workflows from triage to deployment.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/bzellman/earp-kit --skill bug-to-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-to-pr
Source: https://github.com/bzellman/earp-kit/tree/main/skills/system/bug-to-pr
Command: npx skills add https://github.com/bzellman/earp-kit --skill bug-to-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end pipeline from bug report to merged fix PR. Chains bug triage & reproduction → root cause analysis → fix strategy counsel (Opus 4.6 + Codex 5.4 extra high) → targeted implementation → /simplify → /pr-handoff-to-codex with adversarial review → Copilot feedback review → /self-healing-deploy. Use when user reports a bug and expects a delivered fix: "fix this bug", "bug to PR", "debug and fix".

Core Features & Use Cases

  • End-to-end bug resolution workflow that ingests bug reports and delivers merged PRs with auditable steps.
  • Multi-stage governance including root-cause validation, regression risk assessment, and minimal fix strategy.
  • Integrated artifacts: counsels, fix plans, counsel logs, regression tests, and deployment hooks.

Quick Start

Submit a bug report with symptoms and reproduction steps to kick off the /bug-to-pr workflow.

Frequently Asked Questions about bug-to-pr

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

FAQPage Schema
How do I automate the workflow from a bug report to a merged pull request?

Automating a bug-to-PR workflow involves triaging reported issues, reproducing the bug, diagnosing the root cause, and orchestrating a targeted fix. This multi-stage process ensures reproducible fixes, regression testing, and auditable governance before merging.

What is the best way to ensure a bug fix has a minimal blast radius?

To ensure a bug fix has a minimal blast radius, use a multi-stage counsel process that validates the root cause and assesses regression risk. This approach orchestrates targeted implementation and adversarial review before deployment.

How do I add regression testing to an automated bug triage and resolution pipeline?

Regression testing is integrated into an automated bug resolution pipeline by applying tests during the fix strategy and implementation stages. This ensures the fix satisfies reproducible outcomes and maintains auditable governance before deployment.

Can I use an automated bug-to-PR workflow for frontend and backend bugs?

Yes, an automated bug-to-PR workflow applies to product, backend, and frontend bugs. It handles triage, root cause analysis, implementation, and testing across multiple layers by orchestrating cross-team fixes through various agents and tools.

How do I trigger an end-to-end bug resolution workflow with reproduction steps?

To trigger an end-to-end bug resolution workflow, submit a bug report that includes the observed symptoms and reproduction steps. This initiates the triage, analysis, implementation, and review stages required to deliver a merged fix.

Does an automated bug fix pipeline include adversarial code review before deployment?

Yes, an automated bug fix pipeline includes adversarial code review before deployment. It orchestrates a handoff for adversarial review and feedback analysis to satisfy auditable governance and ensure the fix is safe to merge.