verification-before-completion

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

Gate completion claims on fresh verification evidence from tests, builds, and linters.

6|Updated Apr 23, 2026

Search Tags:#verification #build #claims #gate #ci #pull-request #tests

Ready to run

npx skills add https://github.com/ImL1s/flutter-claude-skills --skill verification-before-completion-iml1s

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before claiming completion, teams must rely on verifiable verification evidence; this skill enforces a gate that requires fresh results before acceptance.

Core Features & Use Cases

Ensure completion claims are backed by fresh verification evidence.
Integrate into PRs, releases, and task handoffs to prevent premature success statements.
Provide a repeatable process for running, validating, and reporting verification outputs.

Quick Start

Run the full verification command suite and report the results to prove 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 gate pull request completion with fresh verification evidence?▼

To gate pull request completion, this skill executes your full verification workflow, parses test and build outputs, validates exit codes, and blocks success announcements until evidence meets predefined thresholds.

What is evidence-based verification for code commits and release gates?▼

Evidence-based verification is a gating process that requires running tests, builds, and linters to produce fresh results before any completion claims are accepted for code commits or release gates.

How do I prevent premature success statements in CI pipelines?▼

You prevent premature success statements in CI pipelines by enforcing a verification gate that parses outputs and validates exit codes, ensuring completion claims are backed by fresh verification evidence.

Can I integrate verification checks into task handoffs and pull requests?▼

Yes, you can integrate this verification gate into pull requests, releases, and task handoffs to provide a repeatable process for running, validating, and reporting verification outputs before acceptance.

How do I validate exit codes and test outputs before claiming build completion?▼

You validate exit codes and test outputs by executing the full verification command suite, parsing the results, and gating success announcements only when the fresh verification evidence meets predefined thresholds.

What are the limitations of gating completion with verification evidence?▼

The verification gate requires executing the full verification workflow and relies on predefined thresholds, meaning completion claims cannot be accepted if fresh test, build, or linter evidence is unavailable or fails validation.