bugfix-workflow

Guide end-to-end bug fixing from reproduction through regression testing and ticket documentation.

18|9|Updated Apr 8, 2026

Search Tags:#root cause analysis #verification #regression testing #bugfix #test-first #GitHub issues

Ready to run

npx skills add https://github.com/arozumenko/sdlc-skills --skill bugfix-workflow-arozumenko

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bugfix-workflow
Source: https://github.com/arozumenko/sdlc-skills/tree/main/skills/bugfix-workflow
Command: npx skills add https://github.com/arozumenko/sdlc-skills --skill bugfix-workflow-arozumenko

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you fix a reproducible software bug with a disciplined, evidence-based workflow that prevents unverified changes from slipping into production.

Core Features & Use Cases

Reproduce first: confirms the defect exists and captures exact conditions before coding.
Test-first regression: creates a failing test to lock the bug down and prove the fix.
Root-cause driven change: analyzes the precise cause, implements the minimal fix, then verifies with full checks.
Ticket-ready documentation: posts structured investigation and fix summaries tied to the issue.
Use case: when you see a failing test or a user-reported defect, run the workflow from reproduction through verified fix and document the outcome on the ticket.

Quick Start

Ask your AI agent to run the bugfix workflow for the failing test case and prepare the investigation notes, regression test, root-cause summary, verification steps, and ticket updates.

Frequently Asked Questions about bugfix-workflow

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

FAQPage Schema

How do I fix a reproducible bug end-to-end without introducing regressions?▼

End-to-end bug fixing requires reproducing the defect, writing a failing regression test, isolating the root cause, implementing a targeted fix, and verifying the resolution. This workflow enforces that discipline by requiring a failing test before any code changes are applied.

What is the test-first approach for regression testing during bug resolution?▼

Test-first regression testing creates a failing test that locks down the reported defect before coding begins. The bug is considered fixed only when that previously failing test passes, proving the correction works and preventing future regressions from slipping through.

How do I document root cause analysis and verification steps on GitHub issues?▼

Documenting root cause analysis on GitHub issues involves posting structured investigation notes, regression test details, the minimal fix applied, and full verification results directly as comments on the ticket to maintain a transparent and auditable resolution history.

Can I use this bugfix workflow if I only have a failing test case and no reported GitHub issue?▼

Yes, the workflow applies whenever you have a reproducible defect or failing test case that needs full resolution. It guides you from reproduction through verified fix and generates structured documentation you can attach to an issue or pull request.

Why should I reproduce a software defect before starting root cause analysis?▼

Reproducing the defect first confirms the bug exists and captures the exact conditions under which it occurs. This prevents investigating phantom issues and ensures the root cause analysis targets the actual failure rather than unrelated code behavior.

What's the best way to ensure a bug fix is verified before merging to production?▼

The best way to verify a bug fix is running a structured workflow that reproduces the issue, locks it down with a failing regression test, implements a minimal root-cause-driven change, and passes full verification checks before documenting the outcome on the ticket.