codex-validation

A findings-first validation workflow prioritizes producing structured audit findings before applying fixes. It verifies changed code and surrounding context for correctness and maintainability, then generates prioritized findings, fixes approved issues, and re-verifies before committing.

To perform a manual audit, apply a six-step validation flow: verify the changed code, read surrounding context, produce structured findings, fix approved issues, re-verify the corrections, and commit the finalized changes for a safe handoff.

You need a final validation stream when a project requires a rigorous audit beyond standard code reviews. Use it during final validation to verify that changed code and surrounding context are correct, maintainable, and fully prepared for a safe commit handoff.

Yes, findings-first validation explicitly includes reading surrounding context to assess maintainability and correctness. This step ensures changed code is well-contextualized within the broader project and that issues are identified before producing structured findings.

An end-to-end validation audit enforces a structured six-step flow including context reading, findings generation, and re-verification before commit. A standard code review is less rigorous, whereas findings-first validation ensures deeper correctness and maintainability verification for final streams.

A re-verification step is needed to confirm that approved fixes resolve the original findings without introducing new issues. This ensures the changed code remains correct and maintainable before the final commit, maintaining a safe handoff for the project.