verification-before-completion

Enforce fresh verification evidence before asserting task completion.

Updated Apr 16, 2026

Search Tags:#testing #verification #governance #evidence #quality-assurance #claims #pull-requests

Ready to run

npx skills add https://github.com/HadiCherkaoui/opencode-config --skill verification-before-completion-hadicherkaoui

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification invites risk of delivering incomplete or incorrect results. This Skill enforces fresh verification evidence before any success assertion.

Core Features & Use Cases

Enforces a step-by-step verification protocol prior to status claims.
Guides teams through identifying the proving command, executing it fully, reading the full output, and validating its result.
Use Case: before closing a ticket or merging a PR, run verification and attach the fresh evidence to support the claim.

Quick Start

Run the verification command, review the full output, and only claim completion after verifying 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 enforce verification before claiming a pull request is complete?▼

To enforce verification before claiming a pull request is complete, execute the full proving command, parse the fresh output, and only assert success if the evidence validates your claims. This protocol prevents premature completion claims by requiring fresh test results as proof.

What is the best way to prevent premature completion claims during software delivery?▼

The best way to prevent premature completion claims is to implement a step-by-step governance protocol that requires executing verification commands and reading the full output before any success assertion. This ensures deliverables are backed by fresh evidence.

How does evidence-based quality assurance work for code changes?▼

Evidence-based quality assurance for code changes works by requiring fresh verification outputs to determine status. You must execute the full verification command, parse the results, and only assert success if the fresh evidence confirms the completion claims.

Do I need specific testing frameworks to verify completion with evidence?▼

No specific testing frameworks are required to verify completion with evidence. The process applies to any code changes, test results, or deliverables where you can execute a verification command and parse the output to validate status before asserting success.

When should I run verification commands to support ticket closure claims?▼

You should run verification commands to support ticket closure claims immediately before asserting success. Executing the full verification protocol and attaching the fresh evidence ensures your completion claims are accurate and prevents delivering incorrect results.