Verification Before Completion

You prevent premature completion claims by enforcing an evidence-based verification gate that requires running fresh commands, validating exit codes, and asserting success only from verified output.

Evidence-based verification before a pull request is a quality gate requiring fresh execution of compilation, linting, and tests, ensuring explicit pass criteria are met before declaring completion.

To verify TypeScript compilation and linting before committing, run the full build and lint commands freshly, check their exit codes, and confirm the outputs meet your explicit pass criteria.

Stale test runs cause misleading release readiness because they rely on previous outputs instead of fresh verification, allowing code changes to pass undetected through the quality gate without actual evidence.

Yes, this verification approach works with CI pipelines by enforcing fresh execution of build, test, and lint commands, validating exit codes, and gating release readiness strictly on those outputs.

Common red flags when checking software quality gates include relying on stale runs, accepting unverified agent reports, and using vague confidence language instead of validating fresh command exit codes and outputs.