verification-before-completion

Run verification commands and record output evidence before completion claims.

Updated Feb 5, 2026

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

Ready to run

npx skills add https://github.com/Khoiwall/be_vidify --skill verification-before-completion-khoiwall

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming completion without verification leads to unreliable results and erodes trust. This Skill enforces evidence-based verification before any success claims.

Core Features & Use Cases

Structured verification gates that require running fresh verification commands and reviewing outputs before claiming success.
Evidence-first workflow that captures command outputs, exit codes, and relevant logs to support assertions.
Audit-friendly policy for code reviews and PRs to prevent premature or dishonest completion claims.

Quick Start

Run the full verification workflow and attach the fresh command output as evidence before declaring completion.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I enforce verification before completing a code review or release?▼

Evidence-based verification requires running fresh verification commands, checking exit statuses, and recording explicit outputs before declaring completion. This prevents premature success claims by capturing command outputs and relevant logs as audit-friendly proof.

How do I capture verification evidence for continuous integration outputs?▼

Capture verification evidence by running the full verification workflow and attaching fresh command outputs, exit codes, and logs. This evidence-first workflow supports audit-friendly code reviews and prevents unreliable results from unverified claims.

What is evidence-based verification in software engineering quality assurance?▼

Evidence-based verification in quality assurance requires running fresh verification commands, inspecting outputs, and recording evidence before allowing success claims. It enforces structured verification gates to prevent unreliable results and eroded trust.

How to prevent premature completion claims during testing and release activities?▼

Prevent premature completion claims by enforcing structured verification gates that require fresh output, exit status checks, and explicit evidence recording. This ensures all development, testing, and release activities are validated before success is declared.

Does verification before completion work without external dependencies?▼

Yes, verification before completion operates without external dependencies. It functions as an advanced standalone policy framework to enforce requirements like fresh output and exit status checks for audit-friendly code reviews and continuous integration workflows.