verification-before-completion

Verify completion claims by running verification commands and documenting evidence before status changes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/eugene-belkovich/ai-setup --skill verification-before-completion-eugene-belkovich
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/eugene-belkovich/ai-setup/tree/main/claude/base/skills/process/verification-before-completion
Command: npx skills add https://github.com/eugene-belkovich/ai-setup --skill verification-before-completion-eugene-belkovich

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before claiming work is complete, ensure there is fresh verification evidence and a documented trail to support any success assertions, preventing unverified or dishonest claims.

Core Features & Use Cases

  • Verification gate: enforces running the verification commands, examining outputs, and validating success criteria.
  • Evidence documentation: automatically logs evidence and outcomes to prevent unverified claims.
  • Use Case: Ideal for code reviews, PR approvals, and handoffs where integrity matters.

Quick Start

Run the full verification workflow and log the outcome before marking work as complete.

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 approving a pull request?▼

To enforce verification evidence before a pull request approval, implement a structured gate process that mandates running verification commands, examining outputs, and validating success criteria to prevent unverified completion claims.

What is a verification gate in software engineering quality assurance?▼

A verification gate in quality assurance is a structured process that enforces running verification commands, examining outputs, and validating success criteria before work is marked as complete, ensuring every claim is supported by verifiable outputs.

How do I require fresh verification evidence for project handoffs?▼

To require fresh verification evidence for project handoffs, apply a structured gate process that mandates running verification commands and automatically logs evidence and outcomes to support success assertions across software teams.

How do I prevent unverified claims during code reviews?▼

To prevent unverified claims during code reviews, enforce a verification gate that requires fresh verification evidence and a documented trail, automatically logging outcomes before allowing any work to be marked as complete.

Does this verification process work without external dependencies?▼

Yes, this verification process works without external dependencies, applying a structured gate process across software teams to mandate running verification commands and documenting results for code reviews and PR approvals.

When should I use automated evidence documentation in software engineering?▼

Use automated evidence documentation in software engineering during code reviews, PR approvals, and project handoffs where integrity matters, ensuring there is fresh verification evidence and a documented trail to support success assertions.