verification-before-completion

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

Run verification commands and cite exit codes before claiming task completion.

2|Updated Apr 9, 2026

Search Tags:#testing #verification #build #honesty #status-report #command-run

Ready to run

npx skills add https://github.com/skytiger6724/qwen-skills --skill verification-before-completion-skytiger6724

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill stops premature completion claims by insisting on fresh verification evidence before reporting any success, preserving trust and preventing rework.

Core Features & Use Cases

Verification gate: Identify and run the proving command whenever a test, build, or requirement status is mentioned.
Evidence playback: Read exit codes and full outputs, document failures explicitly, and only claim success with supporting logs.
Use case: Before pushing a change or filing a PR, rerun the relevant test suite, capture the output, and report exactly what succeeded before declaring the work done.

Quick Start

Run the verification command, read each output and exit code, and then report the verified status before declaring completion.

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 completion claims when reporting build or test status?▼

Preventing premature completion claims requires running the relevant verification command, reading its output and exit code, and citing that evidence before asserting success in status reports or pull requests.

What is the best way to verify task completion before pushing a commit?▼

The best way to verify task completion before pushing a commit is to rerun the applicable test suite, capture the full output, and document the exact results before declaring the work done.

How do I document command run evidence for a status report?▼

Documenting command run evidence involves executing the proving command fully, capturing the output logs, and explicitly recording any failures or successes before submitting the status report.

What happens if a verification command fails before a task is marked complete?▼

If a verification command fails, the task cannot be marked complete; the failure must be documented explicitly from the output and exit code before any further success claims are made.

Does verification before completion work with existing development workflows?▼

Yes, it integrates into development workflows by inserting a verification gate that demands hard evidence from command runs before allowing satisfaction claims for commits, pull requests, or handoffs.