What is the main purpose of this skill?

It prevents the AI from claiming a task is finished until it has executed and verified specific commands that prove success with actual output evidence.

When is this skill triggered during the development cycle?

It applies before any success claim, satisfaction expression, code commit, PR creation, or task delegation.

Does this work with regression testing?

Yes, it specifically enforces the Red-Green cycle, ensuring a test fails before the fix and passes after, proving the fix actually addressed the issue.

How does this improve AI-human collaboration?

It builds trust by ensuring that when the AI says a task is 'done,' it is backed by verifiable logs and command results rather than a guess.

Why does this skill ban phrases like 'it should work'?

Using 'should' or 'probably' is a red flag for unverified assumptions; this skill requires hard evidence (like exit code 0) before any success claim can be made.

Verification Before Completion

Name: Verification Before Completion
Author: seanGSISG

byseanGSISG

セキュリティとテスト

Enforces a strict evidence-based workflow by requiring verified command output before any task is marked as complete.

概要

The Verification Before Completion skill implements a rigorous 'Iron Law' for Claude Code, preventing the AI from making premature or unverified claims about work status. By acting as a mandatory gate function, it ensures that every assertion—whether it's a bug fix, a build success, or a passed test—is backed by fresh, complete execution evidence rather than assumptions or previous runs. This skill is essential for maintaining high code quality and developer trust, eliminating 'hallucinated' successes and ensuring that code only moves forward once its functionality is proven via terminal output.

主な機能

Enforces the 'Iron Law' requiring fresh verification evidence for all success claims
Implements a structured Gate Function process (Identify, Run, Read, Verify)
Identifies 'Red Flag' language like 'should' or 'seems to' to prevent rationalization
Requires independent verification of delegated agent tasks before reporting completion
0 GitHub stars
Standardizes patterns for TDD Red-Green cycles and regression testing

ユースケース

Verifying complex project requirements against a line-by-line checklist with evidence
Ensuring full test suites and linters pass with zero failures before opening a PR
Validating bug fixes through mandatory Red-Green test cycles before committing

概要

主な機能

Enforces the 'Iron Law' requiring fresh verification evidence for all success claims
Implements a structured Gate Function process (Identify, Run, Read, Verify)
Identifies 'Red Flag' language like 'should' or 'seems to' to prevent rationalization
Requires independent verification of delegated agent tasks before reporting completion
0 GitHub stars
Standardizes patterns for TDD Red-Green cycles and regression testing

ユースケース

Verifying complex project requirements against a line-by-line checklist with evidence
Ensuring full test suites and linters pass with zero failures before opening a PR
Validating bug fixes through mandatory Red-Green test cycles before committing