verification-before-completion

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

Run verification commands and collect fresh evidence before asserting task completion.

Updated May 15, 2026

Search Tags:#testing #verification #audit #completion #evidence #claims

Ready to run

npx skills add https://github.com/nachopalmeri/agents-system --skill verification-before-completion-nachopalmeri

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In software workflows, teams often claim completion without verifiable evidence. This Skill enforces a discipline where every success claim is backed by fresh verification results, reducing dishonesty and drift.

Core Features & Use Cases

Enforces running explicit verification commands before declaring completion.
Requires analyzing outputs (exit codes, logs, and diffs) to validate success criteria.
Use Case: Before merging a PR, run automated tests and lint checks, attach the results as evidence, then publish the final claim.

Quick Start

Run verification commands on a completed task and report the results with evidence before making any success claims.

Frequently Asked Questions about verification-before-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify task completion claims with fresh evidence before merging a PR?▼

To verify task completion claims, run explicit verification commands like automated tests and lint checks, collect fresh evidence from the outputs, and analyze exit codes and logs before publishing a final success claim.

What is the best way to enforce evidence-first verification for software builds?▼

Evidence-first verification is enforced by running verification commands on completed builds, analyzing the results and diffs to validate success criteria, and requiring command logs to support any completion statements before they are published.

Why does my workflow allow declaring success without verifiable test evidence?▼

Workflows allow premature success claims when explicit verification steps are missing, which this process solves by enforcing automated test execution and output analysis to collect fresh evidence before allowing any completion statements.

How do I stop premature completion statements in automated testing workflows?▼

To stop premature completion statements, implement a discipline that prohibits success claims until automated tests are executed, exit codes are validated, and fresh command results are attached as evidence to support the final claim.

Does this verification process work with standard CI logs and exit codes?▼

Yes, this verification process works with standard CI logs and exit codes by explicitly analyzing them to validate success criteria, ensuring that every completion claim is backed by fresh evidence collected directly from the command outputs.

When do I need to run automated verification checks before asserting task completion?▼

You need to run automated verification checks before asserting task completion whenever a task reaches its final stages, ensuring that automated tests, lint checks, and build outputs are collected as evidence to prevent dishonesty and drift.