verification-before-completion

Run fresh verification commands and analyze output before asserting task completion.

Updated Jan 10, 2026

Search Tags:#code quality #testing #verification #completion #evidence #assertions

Ready to run

npx skills add https://github.com/vrazdalovschi/dotfiles --skill verification-before-completion-vrazdalovschi

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature or unsubstantiated claims of task completion, ensuring that all assertions are backed by fresh, verifiable evidence, thereby maintaining trust and accuracy.

Core Features & Use Cases

Mandatory Verification: Enforces running verification commands before any claim of success, passing, or completion.
Red Flag Identification: Helps identify common rationalizations and "red flag" behaviors that lead to errors.
Use Case: Before committing code, an agent must run the relevant test suite and confirm zero failures in the output, then present this evidence when stating "tests passed."

Quick Start

Before claiming any status or expressing satisfaction, identify, run, read, and verify the command that proves the claim.

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 premature task completion claims in automated code testing?▼

To prevent premature task completion claims, enforce a strict verification protocol requiring fresh execution of testing commands and analysis of their output before any assertion is made. This ensures all success claims are backed by verifiable evidence.

What is evidence-based verification for code quality assertions?▼

Evidence-based verification is a protocol enforcing the execution of verification commands and analysis of their actual output before asserting any task status. It prevents unsubstantiated claims by requiring fresh, verifiable proof for every completion statement.

How do I enforce running test suites before claiming code completion?▼

You can enforce running test suites before claiming completion by applying a mandatory verification protocol. This requires identifying, running, and reading the relevant test suite output to confirm zero failures before stating that tests passed or code is complete.

Why do automated agents claim success without verification?▼

Automated agents often claim success without verification due to common rationalizations and red flag behaviors. Enforcing a strict protocol that requires fresh execution of verification commands prevents these errors and maintains honesty in agentic operations.

Does verification before completion work for deployment and development stages?▼

Yes, verification before completion applies to all stages of work, from development to deployment. It enforces running verification commands and analyzing their output before any assertion is made, preventing premature success claims across the entire workflow.

What are the limitations of relying on assertions without fresh execution evidence?▼

Relying on assertions without fresh execution evidence leads to premature or unsubstantiated claims of task completion. It bypasses the required analysis of actual verification command output, risking errors and eroding trust in automated status reports.