code-review-checklist

To validate a bug-fix before merging, you apply an evidence-based review checklist that verifies task scope, correctness, and repository state. This process checks artifact consistency across progress logs and known issues, producing an explicit approve, reject, or pending decision for the approval gate.

An evidence-based code review checklist is a structured validation procedure that requires access to task artifacts, progress logs, and verification reports. It works by loading session context to verify task identity and ensure artifact consistency before generating a definitive review decision.

Yes, you need repository state files to run a session review for an approval gate. The checklist explicitly requires access to task artifacts, progress logs, verification reports, and repository state files to produce a definitive review decision such as approve, reject, or recovery.

The best way to gate a long-running session in an autonomous agent pipeline is to apply an evidence-based review checklist that validates scope and verification evidence. This produces explicit outcomes like approve, reject, pending, or recovery, and automatically updates relevant repository state files.

Your code review checklist may fail to prevent scope drift and inconsistent artifacts if it lacks structured evidence-based validation. Without verifying task identity, scope, correctness, and repository resumability together, teams often approve code without sufficient evidence, leading to missed verification and artifact misalignment.