Can this skill be used for regression testing?

Yes, it supports strict TDD patterns where the AI must prove a test fails when the fix is reverted and passes when the fix is applied (Red-Green cycle).

How does it handle speculative language like 'should work'?

The skill treats words like 'should', 'probably', and 'seems to' as red flags. It triggers a stop-and-verify protocol that requires the AI to run commands before proceeding.

What is the 'Iron Law' of this skill?

The Iron Law states: 'No completion claims without fresh verification evidence.' It prevents the AI from assuming code works without running the relevant commands in the current session.

Why is this better than standard AI task completion?

It removes 'rationalization' where an AI might think code is correct because it looks right. This skill forces external validation via the terminal, ensuring the code actually executes correctly.

Verification Before Completion

Name: Verification Before Completion
Author: pur3v4d3r

bypur3v4d3r

•

Seguridad y Pruebas

Enforces a strict evidence-based workflow requiring real-time command execution and output verification before any task is marked as complete.

Acerca de

This skill serves as a rigorous quality gate for Claude Code, mandating that all success claims, status updates, and Pull Request readiness be backed by fresh, objective evidence. It implements an 'Iron Law' of verification that prevents premature assertions, 'hallucinated' successes, and the common pitfalls of rationalization. By following a structured Identify-Run-Read-Verify protocol, it ensures that tests, builds, and linting processes are actually executed and confirmed through exit codes and logs before the AI reports completion to the user.

Características Principales

Red-Green TDD verification patterns for regression testing
Automated detection of speculative language and red-flag phrases
Independent verification of delegated agent results and VCS diffs
Mandatory Identify-Run-Read-Verify gate for all status claims
Evidence-based requirement tracking against implementation checklists
1 GitHub stars

Casos de Uso

Confirming a full project build succeeds after major refactoring before creating a PR
Ensuring a bug is truly fixed by verifying original symptoms pass after a code change
Validating that all requirements are met by cross-referencing logs with original project specs

Acerca de

Características Principales

Red-Green TDD verification patterns for regression testing
Automated detection of speculative language and red-flag phrases
Independent verification of delegated agent results and VCS diffs
Mandatory Identify-Run-Read-Verify gate for all status claims
Evidence-based requirement tracking against implementation checklists
1 GitHub stars

Casos de Uso

Confirming a full project build succeeds after major refactoring before creating a PR
Ensuring a bug is truly fixed by verifying original symptoms pass after a code change
Validating that all requirements are met by cross-referencing logs with original project specs