verification-before-completion

Enforce evidence-first verification before claiming work completion.

Updated Dec 20, 2023
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill verification-before-completion-thiago-cruz-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Thiago-Cruz-eng/Hibrygame/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill verification-before-completion-thiago-cruz-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents false or premature “done” claims by forcing verification evidence before you commit, create a PR, or express satisfaction with work quality.

Core Features & Use Cases

  • Verification-gated completion: Requires identifying the specific command that proves the claim, running the full command fresh, and confirming output and exit status before asserting success.
  • Evidence-first status reporting: Guides you to state the actual status with evidence when verification fails, instead of using optimistic wording that implies passing.
  • Common failure detection: Helps avoid typical traps like trusting prior runs, assuming partial checks are sufficient, or relying on an agent’s success message without independent validation.
  • Use Case: Before merging code, you verify tests, lint/build, and any stated fixes with the exact commands whose output demonstrates the claim, then report results honestly.

Quick Start

Ask the AI to help you verify your change by stating the exact verification command you will run, then have it review the fresh command output and only allow you to claim 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 verify code changes before opening a pull request?

Prevent premature completion claims by enforcing evidence-first verification, which requires running the exact proving command fresh and validating its output and exit code before asserting any work is done.

What is evidence-first verification for CI completion criteria?

Evidence-first verification for CI completion criteria is a process that restricts completion language to cases where fresh command output and exit codes actually confirm the claimed success.

How do I stop false completion claims on failed tests or linting?

Stop false completion claims on failed tests or linting by running the full verification command fresh, checking failure counts from the complete output, and reporting the actual status with evidence instead of optimistic wording.

Does verification before completion work with existing testing and linting commands?

Verification before completion works with existing testing and linting commands by requiring you to state the specific command that proves your claim, run it fully, and confirm the exit status before asserting success.

Why should I not trust prior test runs when claiming a build is ready?

You should not trust prior test runs because trusting previous execution results is a common failure trap that prevents honest status reporting and leads to premature completion claims without fresh evidence.