bugfix-workflow

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.

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.

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.

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.

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.

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.