verify-when-complete

A strict verification gate enforces fresh execution of format, lint, build, and test steps before allowing any completion claims for Go development. This prevents unverified completion claims by requiring all checks to pass, avoiding broken commits and failed CI pipelines.

Automatic toolchain detection identifies whether your Go project uses Taskfile, Makefile, or raw Go commands. It then executes the corresponding verification commands without manual configuration, streamlining the pre-commit verification workflow.

CI pipelines fail when completion claims are made without fresh verification of Go code changes. Relying on outdated test results or skipping format, lint, build, and test execution leads to broken commits that fail during continuous integration.

Yes, pre-commit verification works with both Taskfile and Makefile, as well as raw Go toolchains. The system automatically detects your project's build setup and executes the corresponding verification commands to ensure code quality.

To run Go tests with race detection before a pull request, execute fresh verification steps with uncached tests and race detection enabled. This strict verification gate ensures all format, lint, build, and test checks pass before creating a pull request.