verification-before-completion

Run verification commands and inspect output before claiming work completion.

Updated Mar 9, 2026

Search Tags:#code quality #testing #ci/cd #verification #completion #assertions

Ready to run

npx skills add https://github.com/Bigme2020/skills-collection --skill verification-before-completion-bigme2020

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Bigme2020/skills-collection/tree/main/verification-before-completion
Command: npx skills add https://github.com/Bigme2020/skills-collection --skill verification-before-completion-bigme2020

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature claims of work completion by enforcing a strict verification process, ensuring that assertions are always backed by fresh, undeniable evidence.

Core Features & Use Cases

Mandatory Verification: Ensures that any claim of completion, success, or passing status is preceded by running the relevant verification command and examining its output.
Prevents False Claims: Guards against common failures and rationalizations that lead to shipping incomplete or incorrect work.
Use Case: Before committing code, running tests, or declaring a bug fixed, this Skill prompts you to execute the necessary commands and confirm the output, preventing the accidental release of faulty work.

Quick Start

Always run the verification command and check its output before claiming any work is complete.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent premature code completion claims in CI/CD pipelines?▼

Preventing premature code completion claims requires enforcing an evidence before assertions policy that mandates running specific verification commands and checking their output before declaring testing, building, or bug fixing tasks complete.

What does evidence before assertions mean for software testing?▼

Evidence before assertions in software testing means you must execute relevant verification commands and examine their fresh output before claiming any task success, thereby preventing false claims of passing status or bug fixes.

Do I need specific testing frameworks to enforce verification before completion?▼

No specific testing frameworks are required. You can enforce verification before completion in any environment by running and checking the output of your existing build, lint, or test commands before declaring work done.

How to verify bug fixes before declaring work complete?▼

To verify bug fixes before declaring work complete, execute the necessary verification commands and confirm the output shows success, ensuring assertions are backed by fresh evidence and preventing the accidental release of faulty work.

Why does code pass linting but fail during the build process?▼

Code passing linting but failing during the build process indicates incomplete verification. Claiming completion without running and checking all relevant commands leads to false success claims and shipping incorrect or faulty work.