verification-before-completion

Require verification evidence before reporting software work as complete.

Updated Mar 3, 2026

Search Tags:#testing #software engineering #quality assurance #validation #verification #completion

Ready to run

npx skills add https://github.com/zinohome/zinoClaw --skill verification-before-completion-zinohome

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/zinohome/zinoClaw/tree/main/docker-customize/deskclaw-resources/skills/verification-before-completion
Command: npx skills add https://github.com/zinohome/zinoClaw --skill verification-before-completion-zinohome

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inaccurate completion claims by requiring fresh verification evidence before reporting that work is finished, fixed, or successful.

Core Features & Use Cases

Verification Gatekeeping: Requires identifying, running, and reviewing the commands or checks that prove a status claim.
Evidence-Based Reporting: Ensures tests, builds, fixes, requirements, and delegated tasks are confirmed through actual outputs.
Use Case: Apply this Skill before creating a pull request or telling a team that an implementation is complete to ensure the reported state matches verified results.

Quick Start

Use the verification-before-completion skill to check my work and confirm whether it is actually ready to be marked complete.

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 software work before claiming completion?▼

To verify software work before claiming completion, execute validation commands like tests or builds, review their actual outputs, and confirm the results match your status assertions before reporting success.

What is evidence-based reporting in software engineering?▼

Evidence-based reporting in software engineering means ensuring tests, builds, fixes, and requirements are confirmed through actual validation command outputs before reporting the work as finished or successful.

How do I prevent unsupported completion claims in development workflows?▼

Prevent unsupported completion claims in development workflows by applying verification gatekeeping, which requires identifying and running proof commands to confirm results before making status assertions.

Do I need to run validation commands before creating a pull request?▼

Yes, you need to run validation commands before creating a pull request to ensure the reported implementation state matches verified results and prevent inaccurate completion claims.

Can I use verification checks for delegated agent tasks?▼

Yes, you can use verification checks for delegated agent tasks by requiring fresh verification evidence and reviewing outputs to confirm successful results before reporting the delegated work as complete.

What's the best way to confirm a software fix is actually successful?▼

The best way to confirm a software fix is actually successful is requiring fresh verification evidence by executing validation commands, reviewing outputs, and confirming results before making status assertions.