verification-before-completion

Run full verification commands and report fresh outputs before claiming completion.

3|Updated Feb 2, 2026

Search Tags:#build #evidence #verify #lint #claims #tests

Ready to run

npx skills add https://github.com/Dethon/ai-dev-flow --skill verification-before-completion-dethon

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work as complete without verification leads to inaccuracies and dishonest reporting. This Skill enforces an evidence-first approach, outlining a repeatable verification flow and requiring explicit confirmation of results before making any success claims.

Core Features & Use Cases

Structured verification workflow: identify, run, read, verify, and report against the current change.
Applies to PRs, releases, and any completion claim to ensure trust and reduce regressions.
Provides guidance on capturing fresh outputs (exit codes, logs, test reports) as evidence.

Quick Start

Run the full verification sequence for your change: execute tests, lint, and build; provide the exact outputs and exit codes 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 prevent claiming a code change is complete without running tests?▼

Prevent premature completion claims by enforcing an evidence-first verification workflow that requires running tests, lint, and build commands before reporting success. You must capture fresh outputs and exit codes as proof that the change actually works.

What is evidence-first verification for pull requests?▼

Evidence-first verification is a structured workflow that requires executing the full verification sequence and reviewing actual outputs before making any completion claims. It ensures trust and reduces regressions by demanding verifiable results for PRs and releases.

How do I verify build and test outputs before a release?▼

Verify build and test outputs by executing the full verification sequence for your change, then capturing the exact outputs and exit codes as evidence. This structured approach confirms the release readiness through fresh, verifiable results.

Does this verification workflow require any specific testing frameworks?▼

No specific testing frameworks are required. The workflow applies to any PR preparation, release, or completion claim by enforcing the execution of your existing verification commands and reviewing their fresh outputs and exit codes.

What's the best way to enforce verification before reporting task completion?▼

The best way to enforce verification is using a structured workflow that identifies, runs, reads, verifies, and reports against the current change. This approach requires explicit confirmation of fresh test and lint outputs before asserting any success.

Why should I capture exit codes and logs during code verification?▼

Capture exit codes and logs during code verification to provide explicit confirmation of results before making success claims. This evidence-first approach prevents inaccurate reporting and ensures that completion claims are backed by fresh, verifiable outputs.