verification-before-completion

Run the full verification command and report exit codes and logs.

Updated Feb 5, 2026

Search Tags:#testing #verification #evidence #quality-assurance #code-review #continuous-integration

Ready to run

npx skills add https://github.com/tyk-lab/my-ai-skill --skill verification-before-completion-tyk-lab

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification is dishonest; this rule ensures evidence is collected before declarations.

Core Features & Use Cases

Enforces a step-by-step verification workflow: identify the verification command, run it fully, read the output, and only declare success after verification.
Applicable to code, docs, or tasks where formal validation is required before merging, releasing, or signaling completion.

Quick Start

Run the full verification command and report the results; only claim completion after confirming fresh, verifiable evidence.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I verify code completion before merging or releasing?▼

To verify code completion, identify the exact validation command, run it fully to generate fresh output, and review exit codes and logs before claiming success.

What is the best way to enforce a verification workflow for continuous integration?▼

Enforcing a verification workflow requires running the full validation command, reading the output, and only declaring success after confirming fresh, verifiable evidence passes all checks.

How do I collect evidence for code review and quality assurance?▼

Collect evidence for code review by running the full verification command to generate fresh output, then report the actual status with that evidence only if all checks pass.

Can I use this verification process for documentation and non-code tasks?▼

Yes, this verification process is applicable to code, docs, or any tasks where formal validation is required before merging, releasing, or signaling completion.

Why does my task verification fail when I claim completion without solid evidence?▼

Task verification fails because claiming completion without verification is dishonest; this workflow ensures evidence is collected from fresh command output and exit codes before declarations.