verification-before-completion

Enforce verification evidence before any completion claim is made.

Updated Jun 23, 2024

Search Tags:#testing #quality assurance #code review #verification #honesty #process enforcement

Ready to run

npx skills add https://github.com/KyleLeduc/bulk-video-review --skill verification-before-completion-kyleleduc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/KyleLeduc/bulk-video-review/tree/main/.github/skills/verification-before-completion
Command: npx skills add https://github.com/KyleLeduc/bulk-video-review --skill verification-before-completion-kyleleduc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the premature or dishonest claiming of work completion by enforcing a strict verification process before any success assertions are made.

Core Features & Use Cases

Mandatory Verification: Ensures that all claims of completion, passing tests, or bug fixes are backed by fresh, executed verification commands and their output.
Reduces False Positives: Prevents shipping incomplete or broken work by stopping "should work" or "looks good" claims without concrete evidence.
Use Case: Before committing code, an engineer must run the test suite, verify zero failures in the output, and then state "All tests pass" with evidence, rather than assuming it's fixed.

Quick Start

Always run the verification command and check its output before claiming any work is complete or successful.

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 during code review and quality assurance?▼

To prevent false completion claims during code review, enforce an evidence before assertions protocol requiring fresh verification command output prior to declaring any task successful. This eliminates false positives by blocking completion statements without executed testing proof.

Why does bug fix verification fail without running testing commands?▼

Bug fix verification fails without running testing commands because assumptions replace evidence, creating false positives. Enforcing execution of verification commands and reviewing their output ensures any passing status or completion claim is backed by fresh, concrete proof.

What is the best way to enforce process enforcement for honest work completion claims?▼

The best way to enforce process enforcement for honest work completion claims is applying an Iron Law protocol: no completion claims without fresh verification evidence. This mandates running and reviewing verification commands before any success assertion is made.

Can I use automated verification for agentic workflows to stop premature task completion?▼

Yes, you can use automated verification for agentic workflows to stop premature task completion. By mandating the execution and review of verification commands prior to any completion statement, the protocol ensures all success assertions are verifiable and honest.

Does this verification protocol work for general software development or only specific testing frameworks?▼

This verification protocol works for general software development, task management, and agentic workflows. It applies framework-agnostic process enforcement by mandating verification command execution and output review before any completion or passing status is declared.

When should I not rely on assumptions for quality assurance and code review?▼

You should never rely on assumptions for quality assurance and code review when claiming work is complete. Always execute verification commands and review their output to ensure zero failures before stating a bug fix is confirmed or all tests pass.