verification-before-completion

To verify tests and builds before completion, run the exact proving command fresh, read the full output and exit code, and only report success if the evidence shows zero failures. This enforces strict workflow discipline by requiring objective proof.

Verify-before-claim workflow discipline is a quality assurance process that requires running fresh builds, tests, and linting before making any success claims. It prevents broken builds by ensuring developers never assert completion without current, objective evidence from exact proving commands.

To stop premature bug fix claims, run the exact failing test that originally exposed the bug, inspect the full output and exit code to confirm zero failures, and report the passing result with the command and evidence before marking the task complete.

Yes, you can and should use linting and build validation when preparing pull requests. Running these quality assurance checks fresh before finalizing commits ensures your PR contains current, objective evidence that the codebase passes all required verification gates.

Common excuses that lead to failing tests include rationalizing that tests probably pass without running them, assuming previous builds still apply, or ignoring exit codes. These red flag phrases force a pause, requiring fresh verification commands before any completion claims.

You need to validate agent-reported outcomes with fresh evidence whenever an agent claims a task is finalized. Run the exact verification command yourself, read the full output and exit code, and confirm zero failures before accepting the agent-reported success claims.