verification-before-completion

Enforces evidence-based verification before any completion claim is made.

Updated May 28, 2026
One-click install
npx skills add https://github.com/haryelramalho/skills --skill verification-before-completion-haryelramalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/haryelramalho/skills/tree/main/skills/community/verification-before-completion
Command: npx skills add https://github.com/haryelramalho/skills --skill verification-before-completion-haryelramalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents false completion claims by requiring fresh verification evidence before stating that work is done, fixed, passing, or ready.

Core Features & Use Cases

  • Evidence-first workflow: Forces the agent to identify, run, read, and confirm the command that proves the claim.
  • Completion guardrails: Applies before saying a task is finished, a test suite passed, a build succeeded, or a bug was fixed.
  • Commit and PR readiness: Ensures verification happens before committing, pushing, creating pull requests, or handing work off to another agent.

Quick Start

Before you claim success, run the exact verification command for the task, inspect the full output and exit code, and only report completion if the evidence confirms it.

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 false completion claims during software builds and testing?

To prevent false completion claims during software builds and testing, enforce an evidence-first workflow that requires running the exact verification command, inspecting the full output and exit code, and citing fresh evidence before reporting success.

What is build validation and PR readiness verification?

Build validation and PR readiness verification is the process of proving a task is finished by running a specific command, reading its full output and exit code, and confirming the evidence before claiming success or handing off work.

How do I verify bug fixes and regression checks before committing code?

To verify bug fixes and regression checks before committing code, run the proving command for the task, read the full output and exit code, and only report completion if the evidence confirms the fix.

Does this verification workflow apply to pull request creation and agent handoffs?

This verification workflow applies to pull request creation and agent handoffs by ensuring fresh verification evidence is collected and cited before committing, pushing, or transferring work to another agent.

What is the best way to enforce evidence-first testing before claiming success?

The best way to enforce evidence-first testing before claiming success is to establish completion guardrails that block any statement of success until the proving command runs and its output confirms the result.