Can this skill be used with any programming language?

Yes, it is language-agnostic and works by requiring the execution of any standard CLI-based verification tools such as npm test, pytest, or cargo build.

Why is the Verified Completion Gate necessary for AI coding?

It prevents the AI from making premature claims of success, ensuring that every fix or feature is backed by actual command output rather than assumptions.

How does it handle Test-Driven Development (TDD)?

The skill includes specific patterns for red-green cycles, requiring the AI to prove a test fails without the fix before proving it passes with it.

Does this replace my existing CI/CD pipeline?

No, it complements your pipeline by ensuring that Claude performs local verification before code ever reaches the repository or pull request stage.

Verified Completion Gate

Name: Verified Completion Gate
Author: timequity

bytimequity

安全与测试

Enforces rigorous verification protocols by requiring fresh command evidence before any task is marked as complete or fixed.

关于

The Verified Completion Gate skill eliminates premature success claims and 'hallucinated' fixes by establishing a non-negotiable 'Iron Law' for AI behavior: no claim of completion is valid without fresh, real-time verification evidence. It provides a structured five-step gate function that requires the AI to identify specific proof commands, execute them, and analyze the full output before reporting status. This ensures that tests, builds, and requirements are genuinely met rather than just assumed to be correct, significantly increasing the reliability of AI-generated code and fixes.

主要功能

TDD-ready red-green verification cycles to prevent regressions
Cross-referencing checklist for manual requirement verification
Elimination of vague language like 'should work' or 'seems correct'
0 GitHub stars
Standardized verification patterns for tests, linters, and build success
Mandatory gate function requiring command evidence before any status claim

使用场景

Ensuring bug fixes actually resolve symptoms before finalizing a commit
Running comprehensive test suites to validate feature completion
Verifying documentation and requirements coverage against a project plan

关于

主要功能

TDD-ready red-green verification cycles to prevent regressions
Cross-referencing checklist for manual requirement verification
Elimination of vague language like 'should work' or 'seems correct'
0 GitHub stars
Standardized verification patterns for tests, linters, and build success
Mandatory gate function requiring command evidence before any status claim

使用场景

Ensuring bug fixes actually resolve symptoms before finalizing a commit
Running comprehensive test suites to validate feature completion
Verifying documentation and requirements coverage against a project plan