verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: Mario

Enforces verification evidence such as command output and logs before task completion in automated workflows, code reviews, or deployment processes.

4|Updated Apr 30, 2026

Search Tags:#automation #code review #logs #verification #tests

Ready to run

npx skills add https://github.com/0xmariowu/builders-dont-cry --skill verification-before-completion-0xmariowu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/0xmariowu/builders-dont-cry/tree/main/core/skills/verification-before-completion
Command: npx skills add https://github.com/0xmariowu/builders-dont-cry --skill verification-before-completion-0xmariowu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents premature claim of completion by ensuring verification evidence is current and reliable, thereby maintaining quality assurance and accountability.

Core Features & Use Cases

Verification Enforcement: Checks that verification commands with exit codes and logs have been run before declaring task completion.
Scope of Application: Suitable for workflows where confirming the success of code, tests, or configurations is critical before finalizing.
Use Case: A developer completes a feature and wants to confirm tests passed by running this Skill before marking the issue as done.

Quick Start

Use this Skill to verify that the latest test run completed successfully before submitting your final update.

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 premature task completion claims in automated workflows?▼

Preventing premature task completion requires enforcing verification checks that demand up-to-date command output, exit codes, and logs confirming successful execution before finalizing any task.

What is the best way to verify code review evidence before marking an issue as done?▼

The best way to verify code review evidence before marking an issue as done is to run specific verification commands and inspect recent logs to ensure tests passed and configurations succeeded.

How do I enforce test verification in deployment processes?▼

You can enforce test verification in deployment processes by requiring specific verification commands to run successfully and checking that recent logs display current, successful execution results before proceeding.

Does verification enforcement work with existing automated code review tools?▼

Yes, verification enforcement integrates with automated code review workflows by checking that verification commands with exit codes and logs have been run before declaring task completion.

Why do I need up-to-date logs to confirm successful execution before completion?▼

You need up-to-date logs to confirm successful execution because current verification evidence maintains quality assurance and accountability by proving the latest test run actually passed.

When should I not rely on automated verification before completion?▼

You should not rely on automated verification before completion when you cannot run specific verification commands or inspect recent logs, as current evidence is required to confirm successful execution.