verification-before-completion

Verification prevents false completion claims by requiring fresh evidence before any status assertion. Run the full command proving your claim, read the complete output and exit code, and only assert success when evidence confirms it. This eliminates assumptions and ensures integrity across testing, builds, CI/CD, and PR preparation.

Execute the complete test command, count pass/fail results in the full output, check the exit code, and only claim success when evidence shows all tests passed. Never skip verification or assume fixes work—always run fresh, complete commands before making any assertion.

Quality assurance requires a gate function: identify the command that proves your claim, run it in full, read all output carefully, verify the evidence matches your assertion, then make the claim with evidence. This prevents rework by catching incomplete or failed work before status changes.

No. Verification before completion is mandatory—never claim success without fresh evidence. Run the full build command, validate the output and exit code, and only assert completion when output confirms it. Skipping this step creates false assurance and downstream failures.

Verification enforces integrity by blocking premature completion claims. In CI/CD workflows, running full verification commands and validating exit codes ensures only genuinely passing stages advance. This eliminates false negatives, reduces rework, and builds trust in pipeline results.

Before PR creation, run the full verification command for your changes—linting, testing, builds, or all three. Read complete output, check exit codes, count any failures, and only submit the PR when evidence confirms all checks pass. This prevents reviews of broken code.