skills.rest
51hhh
51hhhCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Run verification commands and confirm output before claiming completion.

1|Updated Apr 14, 2026
Search Tags:#testing#verification#pull requests#evidence#regression#builds
One-click install
npx skills add https://github.com/51hhh/BU03 --skill verification-before-completion-51hhh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/51hhh/BU03/tree/main/.github/skills/verification-before-completion
Command: npx skills add https://github.com/51hhh/BU03 --skill verification-before-completion-51hhh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature completion claims by forcing fresh verification before you say work is fixed, passing, or ready to ship.

Core Features & Use Cases

  • Evidence-first workflow: Requires running the exact verification command instead of relying on memory, confidence, or previous results.
  • Completion gatekeeping: Helps before commits, pull requests, bug fixes, regression checks, and any statement that implies success.
  • Use Case: When a test suite, build, or bug fix appears done, this Skill makes you verify the outcome and report the actual result with evidence.

Quick Start

Use this skill when you are about to claim success, then run the relevant verification command and confirm the output before making any completion statement.

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 for bug fixes and pull requests?▼

Prevent premature completion claims by enforcing evidence-first verification, requiring you to run the exact build or test command and read complete output before claiming a bug fix is done.

What is evidence-first verification in software engineering workflows?▼

Evidence-first verification is a workflow mechanism that requires running the full command, reading complete output and exit codes, and confirming evidence before stating a build or test is passing.

Why do I need to verify test output before claiming a build is ready to ship?▼

You need fresh verification to avoid relying on memory or previous results, ensuring your build is actually ready to ship based on current exit codes and complete command output.

Does verification before completion work for agent handoffs and regression checks?▼

Yes, verification before completion applies to agent handoffs and regression checks, forcing you to run the relevant verification command and confirm the actual result before reporting success.

What is the best way to gatekeep completion before making a commit?▼

The best way to gatekeep completion before a commit is to enforce a verification step that requires running the full command and confirming the exit code before making any success statement.

Related Skills

Explore More Software Engineering Skills→
gtappsgtapps
69

test-run

Run hermit test suites and report pass/fail summaries.

Community
Intermediate
DFly7DFly7

verification-before-completion

Run full verification commands and attach output evidence before claiming success.

Community
Intermediate
DethonDethon
3

verification-before-completion

Run full verification commands and report fresh outputs before claiming completion.

Community
Basic
EwallywEwallyw

verification-loop

Execute automated verification checks before claiming task completion.

Community
Advanced