verify-before-done

To ensure task completion, run verification commands like tests, type checks, and health endpoints in your current session. This confirms completeness by producing evidence of successful execution, preventing false claims of completion before deployment.

The best way to prevent false claims of completion is to execute all specified testing and linting commands within your active session. This captures output logs for auditability, providing reliable delivery standards and proof of passing checks.

You can execute multiple validation commands by running a verification process that triggers tests, linters, and health checks like curl endpoints. This records output logs within the session for review, establishing trust in system health.

Yes, you need to specify the verification commands for session validation. The process executes the specified tests, linters, and type checks you define, capturing their output to confirm task completeness and prevent false completion claims.

Running verification checks matters because it produces concrete evidence of successful completion. By executing tests and health endpoints before marking a feature complete, you establish deployment readiness and prevent false claims of completion.