verification-before-completion

To verify build status before a code handoff, run your specific test, lint, and build commands to gather fresh output evidence. This ensures your completion claims are backed by actual exit codes rather than assumptions.

Preventing premature completion claims requires enforcing a verification-first policy that identifies the proving command, runs it, and reports results with concrete evidence. This reflects the real status of tests, lint, and builds.

Enforcing fresh evidence gathering for lint and test checks involves defining success criteria that rely on actual command outputs. You identify the proving command, execute it, inspect the output, and report the concrete results.

You need to run verification commands before reporting task completion during any change or handoff scenarios. Applying verification steps across tests, lint, and builds ensures that the real status is accurately reflected before success is declared.

You cannot assume builds succeed without running the proving command during handoffs. The verification process requires defining and enforcing criteria for success that depend entirely on actual command outputs and exit codes.

Verification before completion requires specific test or lint commands to function correctly. You must identify the exact command that proves your claim and execute it to gather the fresh evidence needed to report a successful status.