verification-before-completion

Code review evidence is enforced by requiring explicit verification outputs like git diffs, test results, or build logs before task completion. This prevents premature closure by mandating fresh proof that code changes are actually verified.

The fresh verification principle requires developers to provide current, explicit evidence such as test outputs or screenshots proving a code change works before claiming a task is done. This prevents unverified changes and regressions.

Stop unverified claims by detecting red flag phrases indicating assumed completion and requiring test outputs or git diffs. This ensures developers provide auditable proof that the bug fix actually works before closing the task.

Evidence-driven completion integrates with standard git workflows by accepting git diffs and build logs as valid verification proof. It mandates these artifacts to create auditable completion records and prevent introducing regressions.

Automated verification relies on the developer providing explicit evidence like test outputs or screenshots. It cannot verify changes if fresh proof is unavailable, meaning tasks cannot be marked complete without generating this required verification data.

Explicit verification evidence is needed whenever marking a development task complete to prevent premature closure. It is required to stop unverified code changes, satisfy auditable completion records, and avoid regressions from assumed fixes.