fix-review

To verify if a commit fixes a security audit finding, you map the audit findings to the corresponding code changes in the commit, assess the fix coverage, and generate a structured status report like FIXED or PARTIALLY_FIXED with supporting evidence.

Tracking partial security remediation across multiple commits involves mapping findings from audit reports to the applied changes, rating the fix quality, and surfacing any remaining security gaps in a structured assessment output.

Commit fix verification works by accepting a source baseline, target commits, and an optional security report, then analyzing the code diffs to determine if the security findings are properly remediated without introducing new bugs.

You can review remediation workflows by providing a source baseline and target commits, as the security report input is optional, allowing you to still analyze code changes and assess fix coverage against known security issues.

To identify remaining security gaps after applying remediation commits, the review process maps the original audit findings to the new code diffs, evaluates the fix quality, and explicitly flags any findings that remain NOT_ADDRESSED.

Yes, end-to-end security remediation across fix branches is supported by mapping audit reports to code changes, assessing the fix coverage of the commits, and generating structured status reports to ensure all findings are properly remediated.