verification-before-completion

Runs verification commands and checks outputs before declaring work complete.

2|1|Updated May 1, 2026

Search Tags:#verification #completion #governance #evidence #quality-assurance #code-review #pull-request

Ready to run

npx skills add https://github.com/LeonardoTan19/metaforge --skill verification-before-completion-leonardotan19

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevent dishonest completion claims by enforcing verification before any success claim.

Core Features & Use Cases

Enforces running explicit verification commands prior to claiming completion.
Provides a structured gate function (IDENTIFY, RUN, READ, VERIFY, ONLY THEN) to ensure evidence-based assertions.
Guards code-review readiness and PR finalization by requiring fresh evidence.

Quick Start

Run the verification commands to verify the current task's status before claiming 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 declaring a pull request complete?▼

Verification before declaring a pull request complete requires running explicit verification commands and validating their outputs as fresh evidence. This structured gate ensures evidence-based assertions and prevents dishonest completion claims during PR finalization.

What is evidence-based verification for code review readiness?▼

Evidence-based verification for code review readiness is a gating mechanism that executes verification commands and checks outputs before claims. It provides fresh proof of success, satisfying quality-assurance requirements prior to handovers or PR submissions.

How do I document verification evidence for software handovers?▼

Documenting verification evidence for software handovers involves executing required verification commands and capturing their outputs through a structured gate function. This validates the current task status against requirements before making completion assertions or final handovers.

Does this verification process work for general software development workflows?▼

This verification process applies to general software development workflows during finalization, PRs, and handovers. It functions in any context requiring verification commands to be run and their outputs checked against requirements before declaring completion.

Why should I run verification commands before claiming task completion?▼

Running verification commands before claiming task completion prevents dishonest or inaccurate success claims. Enforcing an evidence-based gate ensures that the work is validated against requirements using fresh output data before finalization.