bugfix-workflow

To enforce a strict bug fix workflow, you must reproduce the issue, locate the root cause, apply minimal code repair, write unit tests, verify, and generate a report. This prevents unauthorized changes and ensures comprehensive root-cause analysis.

The best way to ensure a root cause fix is by enforcing mandatory issue reproduction before any changes and focusing on root cause analysis. This approach avoids surface patches and guarantees the actual defect is resolved.

Unit testing for every bug is required to prevent similar issues from recurring. By mandating per-bug unit tests during the verification phase, the workflow ensures each fix is validated and quality assurance is maintained.

You cannot fix a software bug if it cannot be reproduced. The workflow enforces a strict reproduction threshold, blocking code modifications until the issue is successfully reproduced to prevent misdiagnosis and incorrect changes.

To handle incomplete information when reproducing an issue, you should actively ask questions. The workflow prompts information gathering when details are insufficient, reducing guesses and misunderstandings during root-cause analysis.