verification-before-completion

To enforce verification before completion, you must run the authoritative verification command, capture its full output and exit code, and present that evidence before making any positive assertion. Missing verification flags as a blocker to committing or declaring success.

Agents often claim tasks are complete without running tests or builds due to a lack of enforced discipline. This skill prevents false completion claims by requiring fresh, observable verification evidence like test suite output and exit codes before asserting success.

To prevent false completion claims in CI builds and pull requests, gate the workflow by running the exact verification command, capturing full output, and attaching the evidence before stating the work passes verification.

The best way to verify agent-generated code changes is to identify the authoritative verification command, run it fully, and capture the complete output and exit code. Explicit evidence must be presented before any positive assertions are accepted.

Yes, you can use this verification gate for local test runs and linting checks. It applies across development workflows including regression validation and continuous integration, requiring explicit evidence and flagging missing verification as a blocker.

Yes, this verification process prevents rationalization when builds fail by providing patterns for tests, builds, and linting with explicit red flags. It requires observable exit codes and output evidence to block committing or declaring success without actual verification.