verification-before-completion

You can enforce build verification and lint checks by running a four-phase verification sequence covering tests, builds, lint, and diff review. This prevents unverified completion by requiring evidence that all checks pass before allowing commits or merges.

Evidence-based completion verification is a workflow that prevents claiming work is complete without proof by enforcing end-to-end checks across tests, builds, and lint. It outputs a structured Verification Complete report to confirm readiness before releases or PRs.

You run test execution and diff review locally before a commit by executing the verification workflow's four phases sequentially. This ensures your code builds, tests pass, and style checks are clean before you create a PR or push changes.

Yes, this verification workflow works for bug fixes and CI pipelines. It applies to software development workflows requiring evidence before releases or merges, using guardrails to prevent premature success claims across CI pipelines and code changes.

The best way to prevent premature success claims during code changes is to enforce a four-phase verification workflow. It requires passing test execution, build verification, lint checks, and diff review before outputting a structured completion report.

Your CI pipeline allows merges without lint or quality checks because it lacks enforced guardrails. Implementing a verification workflow enforces these checks across four phases, preventing premature success claims before merges or releases.