verification-before-completion

Execute validation commands to confirm task completion before declaring work finished.

21|9|Updated May 27, 2026
One-click install
npx skills add https://github.com/cq112233/unibestX --skill verification-before-completion-cq112233
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/cq112233/unibestX/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/cq112233/unibestX --skill verification-before-completion-cq112233

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common pitfall of declaring work finished without actual proof, ensuring that all claims of success are backed by verifiable execution results.

Core Features & Use Cases

  • Evidence-Based Validation: Mandates the execution of specific verification commands before any task can be marked as complete.
  • Failure Prevention: Eliminates reliance on assumptions, partial checks, or unverified agent reports.
  • Use Case: Before submitting a pull request, use this skill to systematically run your test suite and confirm that all tests pass with zero failures, ensuring the code is truly ready for review.

Quick Start

Run the verification-before-completion skill to validate the current state of the project by executing the required test suite and confirming the output.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I enforce verification commands before a pull request submission?

To enforce verification before a pull request submission, you must systematically run your test suite and confirm zero failures. This approach mandates evidence-based validation, eliminating reliance on assumptions before declaring work finished.

What is evidence-based task completion in software development workflows?

Evidence-based task completion is a verification protocol requiring explicit execution of validation commands. It ensures all claims of success are backed by verifiable execution results rather than partial checks or unverified reports.

Why does declaring work finished without objective proof cause failures?

Declaring work finished without objective proof causes failures because it relies on assumptions and unverified agent reports. Enforcing a rigorous verification protocol prevents this pitfall by requiring explicit validation command execution.

Can I use automated task delegation and still ensure quality assurance?

You can ensure quality assurance with automated task delegation by applying an evidence-based validation protocol. This requires executing specific verification commands to provide objective confirmation of success before any automated task is marked complete.

What is the best way to prevent unverified task completion in software engineering?

The best way to prevent unverified task completion is to mandate the execution of specific validation commands. This protocol ensures objective, evidence-based confirmation of success, removing reliance on partial checks before finishing work.