verification-before-completion

Enforce fresh verification evidence before signaling completion in software workflows.

Updated Mar 17, 2026

Search Tags:#verification #evidence #code-quality #ci-cd #code-review #tests

Ready to run

npx skills add https://github.com/Avi977/ace-claude-toolkit --skill verification-before-completion-avi977

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Premature completion claims are common when work is marked as done without verifiable evidence. This skill ensures that every completion claim is backed by fresh verification results.

Core Features & Use Cases

Enforces running a verification command before signaling completion.
Requires capturing and attaching verification outputs to PRs or commits.
Use Case: Before merging a feature branch, run the verification workflow and attach the results to the PR.

Quick Start

Run the verification command on your work and attach the results as 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 evidence before a pull request is merged?▼

To enforce verification evidence before a pull request is merged, you must run a complete verification command, capture its output, and attach the results to the PR as proof of code quality. Success is reported only when this evidence confirms the claim.

What is the best way to prevent premature completion claims in CI/CD pipelines?▼

To prevent premature completion claims in CI/CD pipelines, enforce a workflow that requires running a complete verification command during finalization and reporting success only when fresh output confirms the work is actually verified.

How do I attach test results as evidence to code changes?▼

To attach test results as evidence to code changes, you run the verification workflow across your software development process, analyze the output, and attach those results directly to your commits or pull requests before signaling completion.

Does this verification process work without any external dependencies?▼

Yes, the verification process works without any external dependencies, requiring only your existing software development workflows and a complete verification command to capture fresh evidence before finalizing code changes or releases.

When do I need to run a verification command before signaling code release completion?▼

You need to run a verification command before signaling code release completion whenever finalizing code changes or pull requests, ensuring that every completion claim is backed by fresh, verifiable evidence confirming the work is actually verified.