Can I skip verification if I am confident in the code?

No, the skill's 'Iron Law' dictates that confidence is not evidence. Every claim must be backed by a fresh execution and reading of the verification command output.

When does the verification rule trigger?

The rule applies before any variation of success claims, expressions of satisfaction, or final actions such as committing code, creating PRs, or moving to the next task.

How does it handle agent delegation?

It requires the AI to independently verify changes and test results rather than blindly trusting success reports from delegated sub-agents.

Why do I need the Verification Before Completion skill?

It prevents the AI from making false or premature claims about code completion by requiring empirical evidence from fresh test, build, or linter runs.

Verification Before Completion

Name: Verification Before Completion
Author: jasir

byjasir

보안 및 테스팅

Enforces a mandatory verification protocol requiring empirical evidence before any task is marked as complete or successful.

소개

This skill implements a strict 'evidence-before-assertions' protocol for Claude Code, preventing the AI from making premature success claims or submitting unverified work. By mandating a specific gate function—identifying the verification command, running it, and confirming the actual output—it eliminates common failures like 'it should work' assumptions or relying on outdated test results. It is particularly useful for maintaining high code quality, preventing regressions, and ensuring that all commits and pull requests meet the defined requirements with 100% certainty.

주요 기능

Line-by-line requirements checklist verification
Real-time exit code and output validation
Mandatory gate function requiring fresh command execution
Prevention of success-bias in agent and sub-task reporting
0 GitHub stars
TDD Red-Green cycle enforcement for regression testing

사용 사례

Ensuring all unit and integration tests pass before opening a Pull Request
Validating bug fixes before committing code to a repository
Verifying that a build succeeds in a local environment after major refactoring

소개

주요 기능

Line-by-line requirements checklist verification
Real-time exit code and output validation
Mandatory gate function requiring fresh command execution
Prevention of success-bias in agent and sub-task reporting
0 GitHub stars
TDD Red-Green cycle enforcement for regression testing

사용 사례

Ensuring all unit and integration tests pass before opening a Pull Request
Validating bug fixes before committing code to a repository
Verifying that a build succeeds in a local environment after major refactoring