review

To verify a bugfix resolves the root cause, you need a code review process that checks for symptom-only changes, drift from the diagnosis, and missing edge-case handling. This ensures the fix addresses the true underlying issue.

The best way to review test coverage for regression proof is to verify tests would fail without the fix, align with behavior rather than internals, and provide meaningful coverage beyond mocks to ensure true regression prevention.

To critique a bugfix workflow, evaluate reproduction evidence, analysis artifacts, implementation notes, test verification, and the actual code changes. This produces a structured critique classifying the fix as inadequate, tests incomplete, or solid.

Yes, code review for bugfixes checks for missing edge-case handling, potential correctness problems, and maintainability issues. It evaluates whether the proposed fix truly resolves the reported root cause without introducing new problems.

You should run a test review after the testing phase of your bugfix workflow has completed. It evaluates the fix and accompanying tests to recommend whether to return to fixing, add testing, or proceed with documentation.

A bugfix might pass tests but not fix the original issue if the fix only addresses symptoms or drifts from the diagnosis. A thorough workflow critique verifies tests actually fail without the fix and align with the root cause.