fix-bug

To reproduce a reported bug, describe the defect and run the reproduction workflow against the codebase to validate the issue before applying a fix. This process applies to user tickets, error logs, and failing tests across the source directory.

The best way to root-cause a defect is to isolate the changes and apply the smallest safe diff that resolves the issue. This ensures controlled, minimal modifications to the codebase without introducing unintended side effects while addressing the core problem.

Yes, you need a regression test to fix bugs in your codebase. A regression test that fails before the fix and passes after is required to guarantee the defect is resolved and prevent future regressions from the same incident.

Incident management links to bug fixing by requiring an incident to be linked to the defect resolution. This tracks the root-cause analysis, the minimal diff, and the regression test together for full traceability and incident management.

Yes, you can use this workflow for failing tests across the src directory. The reproduction and root-cause process applies to failing tests to identify the defect and produce a concise fix diff with a guaranteed regression test.