verification-before-completion

To verify code changes before a PR commit, you must execute a full verification command set across tests, lint, and build steps, then report pass/fail status backed by fresh execution evidence.

Evidence-based completion in CI workflows means asserting work is finished only after parsing fresh test, lint, and build outputs to confirm pass/fail status, preventing misleading completion claims.

You standardize checks before merging by enforcing a verification gate that runs the required tests, linters, and builds, collects fresh outputs, and evaluates the results with precise evidence.

Yes, this verification approach works without external dependencies, requiring only your existing development environment to execute the verification suite and parse the outputs for completion claims.

Claiming work is complete without verification fails CI because unverified assertions are risky and misleading, lacking the fresh test, lint, and build evidence required to prove code changes pass.