fix-bugs

To fix QA failures test-first, you reproduce the reported issue by writing a failing unit or integration test, apply minimal code changes to patch the defect, and run the full test suite to verify the fix prevents regressions.

Spec-driven bug resolution involves parsing QA spec files to identify CRITICAL and MAJOR failures, reading relevant source code and architecture documents, writing failing tests to reproduce the defects, patching the code, and appending a standardized Fix Log to the spec.

You reproduce a QA failure by creating a failing unit or integration test that captures the exact defect reported in the QA spec, running it against the current source code to confirm it fails, and then applying minimal code changes to make it pass.

Yes, you need a test runner to execute and verify tests, access to project source code and QA spec files under the specs directory, and commit permissions to record fixes and append standardized Fix Log entries to the specs.

The best way to document fixes in a QA spec file is to append a standardized Fix Log entry after patching the code and verifying the full test suite passes, then commit the changes with a standardized message recording the resolution.

You prevent regressions by writing failing tests that reproduce the original defect, applying minimal code changes to fix the issue, and running the full test suite to verify all tests pass, including re-running original QA checks when possible.