verification-before-completion

Enforce fresh verification evidence before claiming software completion.

69|19|Updated Jan 26, 2026

Search Tags:#verification #evidence #vcs #quality-assurance #code-review #CI

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that any claim of completion or passing status is backed by fresh verification evidence, preventing premature or dishonest assertions.

Core Features & Use Cases

Verification Gatekeeping: enforce running and reviewing verification commands before declaring completion.
Evidence-first Claims: require capturing and presenting command outputs and results as proof.
Workflow Integration: applicable to code reviews, CI pipelines, and task handoffs to ensure quality before closing tasks.

Quick Start

Run the verification command to produce fresh evidence, then present the output 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 claiming code completion?▼

To enforce verification before claiming code completion, gatekeep your workflow by running explicit verification commands across code changes and tests, then presenting the fresh command outputs as evidence before declaring the task done.

What does evidence-based task completion mean in CI pipelines?▼

Evidence-based task completion in CI pipelines means capturing fresh command outputs and test results as explicit proof, ensuring that any assertion of passing status is strictly supported by current verification data before closing tasks.

How do I prevent premature claims of passing status during code reviews?▼

Prevent premature claims of passing status during code reviews by requiring an evidence-first policy that captures and presents explicit verification command outputs from fresh tests and changes before any completion assertions are accepted.

Do I need specific CI tools to require verification evidence before task handoffs?▼

No specific CI tools are required to require verification evidence before task handoffs. You can integrate this strict verification gatekeeping into existing code reviews and CI pipelines by running explicit commands and presenting their outputs.

What is the best way to ensure quality assurance before closing a development task?▼

The best way to ensure quality assurance before closing a development task is to enforce a verification gate that runs explicit tests and code reviews, capturing fresh command outputs as evidence to prevent premature or dishonest assertions.