verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: TEAM-HOUME

Run verification commands and confirm output before claiming task completion.

10|2|Updated Jun 23, 2025

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

Ready to run

npx skills add https://github.com/TEAM-HOUME/HOUME-CLIENT --skill verification-before-completion-team-houme

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/TEAM-HOUME/HOUME-CLIENT/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/TEAM-HOUME/HOUME-CLIENT --skill verification-before-completion-team-houme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents premature claims of task completion or success by enforcing a strict verification process before any assertion is made, ensuring honesty and accuracy.

Core Features & Use Cases

Mandatory Verification: Ensures that all claims of success (e.g., tests passing, bugs fixed, builds succeeding) are backed by fresh, executed verification commands and their output.
Reduces Errors: Prevents shipping incomplete or broken work by catching issues before they are committed or reported.
Use Case: Before reporting that a bug fix is complete, the agent must run the relevant test command, examine its output, and only then confirm the fix if the output shows zero failures.

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 verify code changes before claiming a task is complete?▼

Verify code changes by running the relevant testing, linting, or building commands and checking their actual output. You can only claim task completion after fresh verification evidence confirms zero failures, preventing premature success assertions.

What does an evidence before assertions policy mean for software development?▼

An evidence before assertions policy mandates executing verification commands and confirming their output before reporting any work as done. This process ensures success claims for bug fixes or builds are always backed by tangible, freshly generated proof.

Can I use this verification process for both bug fixing and linting stages?▼

Yes, the verification process applies to all stages of development including bug fixing, linting, and building. It ensures that any claim of tests passing or bugs fixed is validated by executed command output before completion is reported.

Why do agents prematurely declare task completion without running tests?▼

Agents prematurely declare completion when lacking an enforced verification process. Without mandatory checks, success claims lack supporting evidence, which risks shipping broken work because tests were not actually run and confirmed.

How do I stop reporting incomplete bug fixes as resolved?▼

Stop reporting incomplete bug fixes by enforcing a strict verification policy. You must run the relevant test command, examine its output, and only confirm the fix if the output shows zero failures before making any success claims.

What is the best way to ensure assertions of success are accurate in code quality?▼

The best way to ensure accurate assertions is to mandate running verification commands and confirming their output before claiming success. This strict process prevents shipping incomplete work by catching issues through testing before they are reported.