Can this skill prevent common AI coding errors?

Yes, it specifically targets 'hallucinations' of success by flagging words like 'should,' 'probably,' or 'seems' and requiring hard evidence instead.

What is the primary purpose of the Verification Before Completion skill?

The primary purpose is to ensure that Claude never claims a task is finished or a bug is fixed without first running the necessary commands to prove it with actual evidence.

Does this skill support Test-Driven Development (TDD)?

Absolutely. It includes patterns for regression testing that require a Red-Green cycle—verifying the test fails without the fix and passes with it.

How does the 'Gate Function' work?

The Gate Function follows a 5-step process: Identify the proof command, run the full command, read the output and exit codes, verify the claim against the output, and only then make the completion claim.

Verification Before Completion

Name: Verification Before Completion
Author: orbtyapp

byorbtyapp

Seguridad y Pruebas

Enforces a mandatory evidence-first protocol requiring successful command execution before any task is claimed as complete.

Acerca de

This skill acts as a rigorous quality gate for Claude, preventing premature claims of success or completion. It mandates a strict 'Gate Function' that requires identifying, running, and analyzing fresh verification evidence—such as test outputs, build logs, and linter results—before any assertions are made. By eliminating assumptions and phrases like 'it should work' or 'it seems fixed,' this skill ensures that every code change is backed by verifiable data, significantly reducing regressions and maintaining high development standards.

Características Principales

Comprehensive gate function for builds, tests, and linters
Independent verification protocols for delegated agent tasks
0 GitHub stars
TDD Red-Green cycle enforcement for regression testing
Mandatory execution of verification commands before success claims
Detection of success-state red flags and non-committal language

Casos de Uso

Ensuring bug fixes are verified through local regression test execution
Preventing broken builds by requiring exit-code validation before PR creation
Validating project requirements via a line-by-line checklist before handoff

Acerca de

Características Principales

Comprehensive gate function for builds, tests, and linters
Independent verification protocols for delegated agent tasks
0 GitHub stars
TDD Red-Green cycle enforcement for regression testing
Mandatory execution of verification commands before success claims
Detection of success-state red flags and non-committal language

Casos de Uso

Ensuring bug fixes are verified through local regression test execution
Preventing broken builds by requiring exit-code validation before PR creation
Validating project requirements via a line-by-line checklist before handoff