Verification Before Completion

To verify completion, you must execute fresh build and lint commands and evaluate their outputs against clear acceptance criteria before claiming success. This prevents unverified status reporting by enforcing a repeatable flow that documents exactly what commands to run and how to interpret the results.

The best way to enforce validation before commits or PRs is to apply a verification flow that identifies required commands, executes them fresh, and evaluates the outputs. This reduces ambiguity in status reporting by documenting clear criteria for both success and failure.

Defining acceptance criteria for CI tests requires specifying exact verification commands to run, their expected outputs, and documented rules for how to interpret results. This establishes clear success and failure thresholds to validate code changes before completion.

Yes, you can apply this verification flow across broader development workflows. It is designed to validate tests, lint checks, and builds prior to commits or PRs, ensuring that all required code checks are executed and confirmed before a task is marked complete.

Executing verification commands fresh is required to prove completion because it generates current evidence that your code passes all checks. Relying on previous results risks unverified claims, so running commands immediately before status reporting ensures the validation evidence is accurate.