Can this skill be used for linter checks?

Yes, it specifically includes patterns for linter verification, ensuring code is clean and error-free before the AI reports completion.

Why is this better than standard AI coding?

Standard AI may assume a fix works based on logic; this skill forces the AI to prove it works with live command evidence, reducing bugs and broken commits.

What counts as 'verification' for this skill?

Verification requires running the full command, reading the entire output, checking the exit code, and confirming the results match the desired claim.

What does the Verification Before Completion skill do?

It acts as a quality gate that prevents Claude from claiming a task is done until it has successfully run relevant commands (like tests or builds) and verified the output.

Verification Before Completion

Name: Verification Before Completion
Author: a-ariff

bya-ariff

•

安全与测试

Enforces strict command-based verification and evidence gathering before any task is marked as complete.

关于

Verification Before Completion is a high-integrity skill designed to eliminate false success claims and 'hallucinated' fixes within Claude Code. It implements an 'Iron Law' that forbids Claude from claiming a task is finished without executing fresh commands and analyzing real-time output. By mandating a structured IDENTIFY-RUN-READ-VERIFY-CLAIM cycle, this skill ensures that tests pass, builds succeed, and requirements are met with empirical evidence, preventing the shipment of broken code or incomplete features.

主要功能

Mandatory execution of verification commands before status updates
Requirement-to-output mapping for comprehensive feature validation
Rationalization prevention to stop 'should work' assumptions
1 GitHub stars
Standardized verification patterns for builds, tests, and bug fixes
Strict output analysis for exit codes, linter errors, and test failures

使用场景

Validating bug fixes against original reproduction steps with live evidence
Ensuring production builds succeed after complex refactoring sessions
Verifying that unit and integration tests pass before committing code

关于

主要功能

Mandatory execution of verification commands before status updates
Requirement-to-output mapping for comprehensive feature validation
Rationalization prevention to stop 'should work' assumptions
1 GitHub stars
Standardized verification patterns for builds, tests, and bug fixes
Strict output analysis for exit codes, linter errors, and test failures

使用场景

Validating bug fixes against original reproduction steps with live evidence
Ensuring production builds succeed after complex refactoring sessions
Verifying that unit and integration tests pass before committing code