How does it handle regression testing?

It mandates a Red-Green cycle: writing a test, running it to see it pass, reverting the fix to ensure it fails, then restoring the fix to confirm it passes again.

What are considered 'Red Flags' in this skill?

Red flags include using non-committal language like 'should work,' 'probably,' or 'seems to,' as well as expressing satisfaction before actual verification data is available.

Why is the 'Gate Function' important?

The Gate Function ensures the AI identifies, runs, reads, and verifies specific commands before expressing satisfaction or moving to the next task, preventing premature completion claims.

What is the core principle of this Claude Code skill?

The core principle is 'Evidence before claims,' which dictates that no task can be claimed as complete without running fresh verification commands and confirming the output.

Rigorous Verification Guardrail

Name: Rigorous Verification Guardrail
Author: lastdays03

bylastdays03

Security & Testing

Ensures all code changes and task completions are backed by fresh, empirical evidence before making success claims.

About

The Verification Before Completion skill establishes a non-negotiable protocol for AI-driven development, mandating that every claim of success is supported by fresh verification data. It prevents common pitfalls like 'hallucinated' successes or premature completions by enforcing a strict gate function: identifying specific proof commands, executing them, and analyzing the full output before reporting status. This skill is essential for maintaining high trust and code quality, ensuring that builds, tests, and bug fixes are truly functional rather than just appearing correct.

Key Features

Provides a checklist for identifying red-flag phrases like 'should' or 'probably'.
Mandates fresh verification evidence before any success or completion claims.
Enforces TDD red-green cycles to ensure regression tests are valid.
Implements a multi-step gate function for systematic command execution and analysis.
Categorizes specific verification requirements for builds, linters, tests, and bug fixes.
0 GitHub stars

Use Cases

Validating that complex requirements are met through a line-by-line verification checklist.
Ensuring a build is fully functional and lint-free before creating a pull request.
Verifying bug fixes through automated red-green test cycles before committing code.

About

Key Features

Provides a checklist for identifying red-flag phrases like 'should' or 'probably'.
Mandates fresh verification evidence before any success or completion claims.
Enforces TDD red-green cycles to ensure regression tests are valid.
Implements a multi-step gate function for systematic command execution and analysis.
Categorizes specific verification requirements for builds, linters, tests, and bug fixes.
0 GitHub stars

Use Cases

Validating that complex requirements are met through a line-by-line verification checklist.
Ensuring a build is fully functional and lint-free before creating a pull request.
Verifying bug fixes through automated red-green test cycles before committing code.