verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: codingheader

Run verification commands and compare output against expectations before claiming completion.

Updated Jan 28, 2026

Search Tags:#automation #verification #compliance #governance #integrity #quality-assurance

Ready to run

npx skills add https://github.com/CodingHeader/MySkills --skill verification-before-completion-codingheader

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work as complete without verification leads to misinformation and defective releases; this skill enforces evidence-based completion by requiring running verification commands and capturing proof before making success claims.

Core Features & Use Cases

Enforces a verification gate before status updates like PRs, releases, or deployments.
Defines a repeatable process (Identify → Run → Read → Verify → Only then) to ensure evidence-backed claims.
Use cases include software PRs, audits, and deliverable sign-offs where truthfulness and traceability are critical.

Quick Start

Execute the verification command suite on your latest build to confirm all checks pass before marking 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 checks before claiming a task is complete?▼

To enforce verification before completion, identify a verification command that proves success, run the full command suite, read the output, and compare results against expectations. The skill ensures evidence-backed claims by gating status updates until proof is captured.

Why does claiming work as complete without verification lead to defective releases?▼

Claiming completion without verification leads to defective releases because it bypasses evidence-based validation. Without running verification commands and capturing proof, misinformation spreads and untested changes reach production, compromising software integrity and compliance.

What is the best way to automate compliance and integrity checks for a PR sign-off?▼

The best way to automate compliance for PR sign-offs is implementing a repeatable governance process: identify the verification command, run it, read the output, verify against expectations, and only then claim success. This ensures traceability and truthfulness for deliverables.

How do I capture proof that all build checks pass before marking a release?▼

To capture proof before a release, execute the verification command suite on your latest build, read the output to verify all checks pass, and record the evidence. This quality-assurance step guarantees only evidence-backed completions are marked as successful.

Does this evidence-based completion workflow require any specific dependencies or components?▼

No dependencies or components are required to use this evidence-based completion workflow. The skill operates independently to enforce governance and quality-assurance by defining a repeatable process to identify, run, read, verify, and claim success.

When do I need an automated verification gate for deliverable sign-offs?▼

You need an automated verification gate for deliverable sign-offs when truthfulness and traceability are critical, such as during software PRs, audits, or deployments. It prevents misinformation by requiring captured proof before any status is updated to complete.