final-check

A final quality gate enforces last-step validation by checking repository state, documentation updates, and test results before task approval. It issues a veto when violations are detected, blocking submission until all checks pass.

A final-check validation gate ensures project release readiness by verifying that codebase knowledge was consulted, documentation is updated, and tests pass. It relies on deterministic git diffs and changelog updates to issue vetoes for any unresolved violations.

Yes, you can block task submission by enforcing a validation gate that cross-checks documentation updates. The gate issues a veto listing specific violations when it detects missing changelog updates or incomplete docs, preventing approval until resolved.

To re-validate a project after fixing violations, run the final-check gate again across the repository. It re-checks the git diffs, documentation, and test results to ensure all previously flagged issues are resolved before allowing task submission.

Yes, the final-check quality gate relies on deterministic repository state including git diffs, changelog updates, and test results. It validates task delivery by cross-checking these elements and issuing a veto if any violations are detected.

Use a veto gate for software delivery approval at project completion to ensure all required skills were consulted, documentation is updated, and tests pass. It provides last-step validation by blocking approval until all detected repository violations are resolved.