verification-before-completion

Run verification commands and review output before claiming task completion.

Updated Feb 18, 2026

Search Tags:#code quality #testing #verification #completion #evidence #assertions

Ready to run

npx skills add https://github.com/ollieb89/openrepo --skill verification-before-completion-ollieb89

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the premature declaration of work as complete, fixed, or passing by enforcing a strict verification process before any success claims are made. It combats the inefficiency and unreliability caused by making assertions without concrete evidence.

Core Features & Use Cases

Mandatory Verification: Ensures that verification commands are run and their output is reviewed before any claim of completion or success.
Evidence-Based Claims: Promotes a culture of honesty and reliability by requiring proof before statements.
Use Case: Before committing code, a developer must run the test suite and confirm zero failures, then present the test output as evidence of completion.

Quick Start

Use the verification-before-completion skill to ensure all tests have passed before claiming the task is complete.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

What happens if I claim work is fixed without running verification commands?▼

If you claim work is fixed without running verification commands, you violate the strict protocol that combats inefficiency and unreliability. The process mandates that no assertions of completion, fixed, or passing statuses can be made without concrete evidence from command outputs.

How do I enforce running tests before claiming code completion?▼

To enforce running tests before claiming code completion, you need a strict verification protocol that requires executing specific commands and reviewing their output as evidence before any success assertions are made. This prevents premature declarations of work being fixed or passing.

What is evidence-based verification for bug fixes and code commits?▼

Evidence-based verification for bug fixes and code commits is a protocol requiring concrete proof, such as passing test suite output, before asserting a task is complete. It combats unreliability by ensuring no success claims are made without running verification commands.

How to prevent premature status updates before code verification?▼

You can prevent premature status updates by implementing a mandatory verification process that requires reviewing command outputs first. This ensures developers cannot claim work is passing or complete without presenting concrete evidence from their test suite runs.

Does this verification protocol apply to pull requests and code commits?▼

Yes, this verification protocol applies to all stages of task completion, including code commits, pull requests, and status updates. It requires running verification commands and reviewing their output before asserting success across every phase of the workflow.

What is the best way to verify work completion before a pull request?▼

The best way to verify work completion before a pull request is to run the test suite, confirm zero failures, and present the test output as evidence. This evidence-based approach guarantees assertions of success are backed by concrete proof.