verification-before-completion

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

Run fresh verification commands before declaring tasks complete in workflows.

4|Updated Jan 10, 2026

Search Tags:#verification #completion #evidence #builds #code-review #tests

Ready to run

npx skills add https://github.com/atxinsky/skills --skill verification-before-completion-atxinsky

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents premature completion claims by enforcing fresh verification before asserting success, ensuring evidence-based decisions.

Core Features & Use Cases

Verification Gate: Run fresh verification commands and evaluate their outputs before declaring completion.
Evidence-Driven: Capture exit codes and failure counts as proof of state, reducing misstatements.
Use Case: Before merging a PR or marking a task complete, run the verification sequence to validate tests, builds, and artifacts.

Quick Start

Run the verification workflow to confirm the current task's status, then decide whether to declare completion based on the 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 checks before declaring a development task complete?▼

To enforce verification before completion, run fresh verification commands and evaluate their outputs prior to any success claim. This validates tests, builds, and code reviews, ensuring evidence-based decisions and preventing premature completion statements.

What is evidence-driven task completion in software engineering?▼

Evidence-driven completion is the practice of capturing exit codes and failure counts as proof of state before marking a task complete. It requires inspecting outputs and producing explicit results to prevent misstatements about build or test status.

How do I validate tests and builds before merging a pull request?▼

You validate tests and builds by running a verification sequence that checks the current task status. This workflow inspects outputs and captures explicit evidence, allowing you to decide whether to declare completion based on actual results.

Does this verification workflow require any external dependencies or components?▼

No, this verification workflow does not require external dependencies or components. It functions as a standalone gate to enforce fresh verification commands and capture evidence directly within your existing development and automation environments.

Why should I use a verification gate instead of trusting my build process?▼

A verification gate prevents premature completion claims by requiring fresh validation before asserting success. It captures exit codes and failure counts as proof of state, reducing misstatements and ensuring outputs are explicitly inspected.