verification-before-completion

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

Enforce fresh verification evidence before claiming completion in tests, builds, and code reviews.

1|Updated Apr 22, 2026

Search Tags:#verification #evidence #ci-cd #quality-assurance #tests #auditable-output

Ready to run

npx skills add https://github.com/xiaobin/superpowers-kimi --skill verification-before-completion-xiaobin

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification is dishonest; this skill enforces evidence-based verification before any completion claims to ensure accuracy and auditable traceability.

Core Features & Use Cases

The Iron Law: always run fresh verification commands and read full outputs before claiming success.
The Gate Function workflow: IDENTIFY, RUN, READ, VERIFY, and ONLY THEN claim status to guard against premature conclusions.
Risk mitigation: clear procedures for red flags, failure handling, and keeping an auditable log of verifications.

Quick Start

Run the verification command, review the full output, and only claim completion if verification confirms success.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent AI agents from claiming code completion without running tests?▼

To prevent premature code completion claims, enforce fresh verification evidence by identifying proving commands, running them fully, reading outputs, and verifying results before any success statements. This ensures agents produce auditable outputs before PRs or releases.

What is evidence-based verification in CI-CD pipelines?▼

Evidence-based verification in CI-CD pipelines is the process of executing fresh test or build commands and reading their full outputs to confirm success. It enforces step-by-step verification to ensure accuracy and auditable traceability before releases.

How to enforce step-by-step verification before creating a pull request?▼

To enforce step-by-step verification before a pull request, apply a gate function workflow: identify the proving command, run it fully, read the output, verify the result, and only then claim completion status to guard against premature conclusions.

Can I use automated verification to improve quality assurance for builds?▼

Yes, you can use automated verification to improve quality assurance for builds by enforcing the iron law of always running fresh verification commands and reviewing full outputs before claiming success, ensuring accuracy and mitigating risk.

What should an AI agent do when verification tests fail during a build?▼

When verification tests fail during a build, the agent must handle the failure by recognizing it as a red flag, avoiding any success claims, and keeping an auditable log of the verification results for risk mitigation.

Does verification-before-completion work with code reviews and test suites?▼

Yes, verification-before-completion applies to tests, builds, and code reviews by guiding agents to produce auditable outputs through fresh verification, ensuring completion is only claimed after confirming success.