verification-before-completion

Prevent premature completion claims by enforcing an evidence-first verification workflow that requires running tests, lint, and build commands before reporting success. You must capture fresh outputs and exit codes as proof that the change actually works.

Evidence-first verification is a structured workflow that requires executing the full verification sequence and reviewing actual outputs before making any completion claims. It ensures trust and reduces regressions by demanding verifiable results for PRs and releases.

Verify build and test outputs by executing the full verification sequence for your change, then capturing the exact outputs and exit codes as evidence. This structured approach confirms the release readiness through fresh, verifiable results.

No specific testing frameworks are required. The workflow applies to any PR preparation, release, or completion claim by enforcing the execution of your existing verification commands and reviewing their fresh outputs and exit codes.

The best way to enforce verification is using a structured workflow that identifies, runs, reads, verifies, and reports against the current change. This approach requires explicit confirmation of fresh test and lint outputs before asserting any success.

Capture exit codes and logs during code verification to provide explicit confirmation of results before making success claims. This evidence-first approach prevents inaccurate reporting and ensures that completion claims are backed by fresh, verifiable outputs.