What is the primary purpose of this skill?

The primary purpose is to ensure that no work is claimed as 'fixed' or 'complete' without fresh terminal output or logs proving the assertion.

How does the 'Gate Function' work?

It follows a five-step process: Identify the proof command, Run the full command, Read the entire output, Verify the output confirms the claim, and only then make the claim.

Why is this better than standard status updates?

It eliminates 'false completion' errors caused by fatigue or overconfidence by requiring objective evidence (exit codes, failure counts) over subjective feelings.

Can I use this for regression testing?

Yes, it specifically mandates a Red-Green cycle where you must prove the test fails without the fix and passes with it to confirm the logic.

Verification Before Completion

Name: Verification Before Completion
Author: eyadsibai

byeyadsibai

Security & Testing

Enforces rigorous, evidence-based confirmation through command execution before any work is marked as complete or committed.

About

The Verification Before Completion skill implements a strict 'Iron Law' for software development workflows, mandating that no success claims be made without fresh, verifiable evidence. It acts as a critical gate function within the development process, requiring developers and AI agents to identify specific proof commands, execute them, and analyze the full output before making any assertions about code status. By eliminating assumptions like 'it should work' or 'I'm confident,' this skill prevents broken builds, regressions, and incomplete features from reaching production.

Key Features

Evidence-based reporting for tests, builds, and linting
Anti-rationalization framework to prevent premature commits
TDD Red-Green cycle enforcement for bug fixes
Comprehensive requirement checklist validation
Standardized five-step verification gate function
0 GitHub stars

Use Cases

Verifying bug fixes through documented red-green regression testing patterns
Confirming successful build completion and linter cleanliness after refactoring
Ensuring all unit and integration tests pass with zero failures before PR creation

About

Key Features

Evidence-based reporting for tests, builds, and linting
Anti-rationalization framework to prevent premature commits
TDD Red-Green cycle enforcement for bug fixes
Comprehensive requirement checklist validation
Standardized five-step verification gate function
0 GitHub stars

Use Cases

Verifying bug fixes through documented red-green regression testing patterns
Confirming successful build completion and linter cleanliness after refactoring
Ensuring all unit and integration tests pass with zero failures before PR creation