Does this skill work with linters and build tools?

Yes, it provides specific patterns for linter checks, build success verification, and regression testing to ensure no part of the dev cycle is skipped.

How does it handle tasks delegated to other agents?

It requires the AI to independently verify the changes in the VCS diff and run verification commands rather than trusting the sub-agent's success report.

What is the primary goal of the Verification Before Completion skill?

The primary goal is to ensure honesty and accuracy by requiring hard evidence (like passing test logs or exit codes) before the AI can claim a task is done.

Why can't the AI just say 'it should work'?

This skill categorizes 'should work' or 'probably' as red flags. It mandates that confidence must be replaced by evidence from a fresh command run.

Strict Verification Before Completion

Name: Strict Verification Before Completion
Author: yang0

byyang0

0•

Security & Testing

Enforces a mandatory evidence-based protocol requiring fresh command output before any coding task can be claimed as complete or fixed.

This skill acts as a rigorous gatekeeper for your development workflow, preventing the AI from making premature or unverified success claims. It establishes an 'Iron Law' that requires the identification, execution, and analysis of specific verification commands—such as tests, builds, or linters—before any work is marked as finished. By mandating hard evidence over assumptions, it builds developer trust, eliminates 'hallucinated' fixes, and ensures that code changes are genuinely functional and regression-free before they reach the commit or PR stage.

Key Features

01Standardizes verification patterns for builds, tests, and linter checks

02Prevents linguistic rationalizations like 'should work' or 'seems correct'

03Implements TDD red-green cycle verification for regression testing

04Requires line-by-line requirement checklists before task handover

050 GitHub stars

06Mandates fresh command execution for every completion claim

Use Cases

01Verifying that agent-delegated tasks meet all project requirements with evidence

02Validating bug fixes against original symptoms before committing code

03Ensuring full test suite compliance after complex refactoring sessions

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add yang0/superpower verification-before-completion

For use in Claude.ai and ChatGPT

Key Features

01Standardizes verification patterns for builds, tests, and linter checks

02Prevents linguistic rationalizations like 'should work' or 'seems correct'

03Implements TDD red-green cycle verification for regression testing

04Requires line-by-line requirement checklists before task handover

050 GitHub stars

06Mandates fresh command execution for every completion claim

Use Cases

01Verifying that agent-delegated tasks meet all project requirements with evidence

02Validating bug fixes against original symptoms before committing code

03Ensuring full test suite compliance after complex refactoring sessions

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add yang0/superpower verification-before-completion

For use in Claude.ai and ChatGPT