Verified:GitHub

verification-before-completion

Enforces evidence-based completion claims by mandating verification commands and adversarial self-checks before declaring success.

1|Updated Jan 10, 2026

Search Tags:#testing #verification #completion #evidence #assertions #claims

Ready to run

npx skills add https://github.com/tomwangowa/agent-skills --skill verification-before-completion-tomwangowa

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature or unsubstantiated claims of work completion, ensuring that all assertions are backed by fresh, verifiable evidence, thereby maintaining trust and accuracy.

Core Features & Use Cases

Evidence-Based Claims: Mandates running verification commands before any statement of completion, success, or satisfaction.
Adversarial Self-Verification: Guides the user through a process of identifying and attacking assumptions to uncover potential flaws.
Use Case: Before committing code, this Skill forces you to run tests, check build status, and explicitly document any unverified aspects, preventing the accidental shipment of incomplete or broken work.

Quick Start

Use the verification-before-completion skill to ensure all tests pass and document any unverified aspects before claiming the bug is fixed.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I stop making premature claims of work completion?▼

Prevent premature work completion claims by enforcing an evidence-before-assertion protocol that mandates running verification commands and adversarial self-analysis before declaring success.

What is adversarial self-verification in software development?▼

Adversarial self-verification in software development is a process of identifying and attacking your own assumptions to uncover potential flaws, ensuring all success claims are backed by fresh, verifiable evidence.

How do I verify code before committing and claiming a bug is fixed?▼

Verify code before committing by running tests, checking build status, and explicitly documenting any unverified aspects, which prevents the accidental shipment of incomplete or broken work.

Does evidence-based verification require explicit documentation of unverified work?▼

Evidence-based verification requires explicit documentation of both verified and unverified aspects of the work, maintaining trust and accuracy by ensuring assertions are backed by fresh evidence.

When should I use an evidence-before-assertion protocol?▼

Use an evidence-before-assertion protocol at all stages of development, testing, and deployment where success is declared, ensuring statements of completion are always supported by verifiable evidence.