bugfix

The best way to structure bug fixes is to use a regression-test-first workflow. You reproduce the defect, diagnose the root cause, implement a minimal fix, verify the blast radius, and update durable artifacts like specs and AGENTS.md to ensure changes are auditable.

To perform root cause analysis on failing tests, you reproduce the issue with the smallest reliable scenario, collect evidence, and classify the underlying cause. This structured approach ensures your subsequent code fixes address the core defect without collateral damage.

To document incident management resolutions, you update durable artifacts like specs, tests, AGENTS.md, and workflow docs. This reflects the code changes made during defect resolution and provides an auditable trail for future code review and regression testing.

Yes, you can use a test-driven approach to fix bugs across software projects. You add regression tests before implementing fixes to establish the bug's contract gap, then verify the minimal fix across the entire blast radius to prevent future incidents.

You should update specs and AGENTS.md after a code defect fix to prevent recurrence and maintain durable documentation. Updating these related artifacts ensures the defect resolution workflow is auditable and coordinates durable changes across the team.

When regression testing reveals collateral damage, you should re-evaluate the blast radius of your minimal fix. Revisit your root cause analysis to ensure the code defect fix addresses the core issue without introducing new failing tests or regressions.