test-rigor-enforcement

To enforce test-first development, use a skill that mandates writing tests before implementing new logic and blocks commits that skip tests. This ensures test-first discipline is applied automatically during code generation.

Test-first enforcement in CI/CD requires that comprehensive, deterministic tests covering edge cases are written before new code is committed. It acts as a fail-closed gate to prevent regressions and maintain high code quality.

You validate deterministic tests and edge case coverage by applying enforcement checks that verify tests are not reliant on external state and confirm coverage for null inputs, boundary values, and malformed data before code commits.

Yes, you can block code commits using fail-closed gates that enforce zero-tolerance for test skipping. The enforcement mechanism validates that all code surfaces have adequate test coverage before allowing a commit to proceed.

Yes, test rigor enforcement mandates an AST dependency graph backing during code generation. This structural backing ensures that constitutional testing requirements are accurately validated against the codebase.

You should use automated test discipline enforcement when modifying critical logic, such as scoring algorithms, to prevent regressions. It ensures all code changes meet stringent testing and evidence requirements before integration.