verification-before-completion

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

Run verification commands and report evidence before claiming completion.

223|23|Updated Dec 19, 2025

Search Tags:#verification #build #PR #tests #verification-before-completion

Ready to run

npx skills add https://github.com/ReinaMacCredy/maestro --skill verification-before-completion-reinamaccredy

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents claiming work is complete without explicit verification, enforcing evidence-based completion.

Core Features & Use Cases

Iron Law: No completion claims without fresh verification outputs.
Gate function: A 5-step process (identify, run, read, verify, proceed).
Red flags: Recognizes assertions without evidence and warns.

Quick Start

Run the verification command, read the output, and only then claim completion with 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 my code before claiming a PR or commit is complete?▼

Verification before completion means running your build or test commands fresh, reading the full output, checking exit codes, and confirming success before pushing or opening a PR. Only make completion claims when you have current evidence in hand, not assumptions.

What's the best way to avoid false completion claims in development workflows?▼

Enforce a verification gate: identify the right command for your project (build, test, lint), execute it, review the output completely, and verify the exit code signals success. This 5-step cycle catches failures before they reach PRs or merges.

When should I run verification—before commits, pushes, or PRs?▼

Run fresh verification before each boundary: before committing work, before pushing to a branch, and before opening a PR. Verification at every gate prevents incomplete or broken code from advancing through your workflow.

Can verification catch issues my initial test run missed?▼

Yes. Running verification fresh each time—not relying on earlier test results—catches state changes, dependency shifts, or environment drift that earlier runs missed. Fresh output always reveals the current truth.

What happens if I skip verification and claim work is done?▼

Without verification evidence, you risk pushing broken code, failing CI/CD pipelines, or merging incomplete work. Verification enforces accountability: no completion claim without output proof.