fix-review

To verify security audit findings in git commits, you can compare source and target commits to analyze differential changes. This process maps remediation commits to specific findings and produces a structured report with per-finding status and rationale.

The best way to map TOB-style findings to remediation commits is through evidence-based verification. This approach documents the fix status for each finding by mapping commits directly to the findings and providing traceable rationale.

To ensure security fixes do not introduce new bugs, you perform differential analysis between source and target commits. This identifies changes related to audit findings and verifies the remediation without unintended side effects.

Yes, you can generate evidence for audit workflows from git diff analysis. The process produces structured outputs containing per-finding status, commit references, and actionable recommendations to feed issue writers and reporter tools.

You do not need a security report path to analyze fix branches, as it is optional. Providing source and target commits is sufficient to generate a summarized status and per-finding evidence to guide reviewer decisions.