What counts as valid verification evidence?

Valid evidence is direct terminal output from commands like test runners, build scripts, or linters showing successful execution and an exit code of zero.

Why does this skill require fresh verification?

Fresh verification prevents false positives and ensures that recent changes haven't introduced regressions since the last check, maintaining a high standard of code integrity.

When should this skill be activated?

It should be used whenever you are about to claim a task is done, a bug is fixed, or a code phase is ready for commit or review.

Does this skill replace automated CI/CD pipelines?

No, it acts as a local pre-commit guardrail to ensure quality before code ever reaches the shared CI/CD environment, reducing pipeline failures.

Verification Guardrail

Name: Verification Guardrail
Author: gvarela

bygvarela

セキュリティとテスト

Enforces rigorous verification procedures to ensure all completion claims are backed by fresh, evidentiary test and build results.

概要

The Verification Guardrail skill transforms how Claude handles task completion by mandating fresh, evidentiary proof before any success assertions are made. It eliminates guesswork, false positives, and speculative language by requiring a strict cycle of identifying, running, and analyzing verification commands—such as test suites or build scripts—before updating status or committing code. By prioritizing evidence over assertions, this skill ensures that 'done' truly means verified and functional.

主な機能

Integrates verification logic into status update workflows
Eliminates speculative language like 'should work' or 'probably fixed'
Structured framework for validating builds, tests, and bug fixes
0 GitHub stars
Strict enforcement of the 'Evidence Before Claims' iron law
Mandates execution of fresh verification commands for every claim

ユースケース

Ensuring unit tests pass before merging or committing code
Validating bug fixes with fresh regression test execution
Confirming successful build processes before marking milestones as complete

概要

主な機能

Integrates verification logic into status update workflows
Eliminates speculative language like 'should work' or 'probably fixed'
Structured framework for validating builds, tests, and bug fixes
0 GitHub stars
Strict enforcement of the 'Evidence Before Claims' iron law
Mandates execution of fresh verification commands for every claim

ユースケース

Ensuring unit tests pass before merging or committing code
Validating bug fixes with fresh regression test execution
Confirming successful build processes before marking milestones as complete