What happens if a verification step is skipped?

The skill treats skipped steps as a failure in reporting integrity, forcing the AI to stop and perform the required fresh checks before it can proceed.

Why is this verification skill necessary?

It prevents the AI from making false or premature claims about code status by requiring actual command output as evidence before any task is marked as finished.

Which languages and frameworks does it support?

It is language-agnostic and works with any command-line interface tool, including npm, pytest, go test, golangci-lint, and custom shell scripts.

Does it help with identifying flaky tests?

Yes, by mandating fresh runs and full output reading rather than relying on memory, it helps identify inconsistent test results and environmental issues.

Verification Guardrail

Name: Verification Guardrail
Author: sharpner

bysharpner

•

보안 및 테스팅

Enforces a strict, evidence-based verification protocol to ensure all code changes, builds, and tests pass before marking tasks as complete.

소개

The Verification Guardrail skill implements a non-negotiable 'evidence before claims' policy for Claude, preventing premature declarations of success. It mandates a 5-step validation process—Identify, Run, Read, Verify, and Claim—across all development tasks including testing, building, and linting. By eliminating assumptions and speculative language like 'should work' or 'seems to,' this skill ensures that every reported fix or feature is backed by fresh command output and verified exit codes, significantly increasing reliability and trust in AI-driven development workflows.

주요 기능

Real-time validation for builds, unit tests, and linting
1 GitHub stars
Mandatory 5-step verification gate (Identify, Run, Read, Verify, Claim)
Automated 'red flag' detection for speculative or unverified language
Standardized verification reporting format with command evidence
Zero-tolerance policy for shortcuts and unverified success claims

사용 사례

Ensuring all unit and integration tests pass before submitting a pull request
Validating that production builds and linting rules are clean before deployment
Confirming bug fixes are actually resolved through rigorous reproduction steps

소개

주요 기능

Real-time validation for builds, unit tests, and linting
1 GitHub stars
Mandatory 5-step verification gate (Identify, Run, Read, Verify, Claim)
Automated 'red flag' detection for speculative or unverified language
Standardized verification reporting format with command evidence
Zero-tolerance policy for shortcuts and unverified success claims

사용 사례

Ensuring all unit and integration tests pass before submitting a pull request
Validating that production builds and linting rules are clean before deployment
Confirming bug fixes are actually resolved through rigorous reproduction steps