code-review-follow-up

Post-fix code review verification requires previous findings and fix range metadata to validate each repair. The process applies a read-only workflow against the target repository, outputting per-item dispositions like resolved, unresolved, or accepted-risk with supporting evidence anchors.

Disposition classification in code review follow-up categorizes prior findings as resolved, unresolved, accepted-risk, not-reproducible, or residual-risk. It validates previous findings against current code changes and outputs per-item statuses with evidence anchors and optional reviewer notes.

Classifying pull request dispositions requires access to previous code review findings and fix range metadata. The process operates as a read-only validation within the target repository to re-evaluate prior findings and produce evidence-anchored per-item statuses.

Yes, you can validate unresolved code review findings using a read-only workflow in the target repository. It re-evaluates past findings against current code using fix range metadata, confirming resolved, unresolved, or accepted-risk statuses without modifying the repository.

You need to re-evaluate past code review findings when repairs are made in a pull request workflow. This post-fix verification step checks each previous finding against the current code to confirm its disposition, validating fixes with evidence anchors before merging.