verification-before-completion

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

Run verification commands and review output before claiming work completion.

154|1|Updated Feb 20, 2026

Search Tags:#verification #completion #quality #software #ci #checks

Ready to run

npx skills add https://github.com/haojing8312/WorkClaw --skill verification-before-completion-haojing8312

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents premature claims of success by ensuring that every completion statement is backed by fresh verification evidence, eliminating dishonesty and re‑work caused by unchecked assertions.

Core Features & Use Cases

Verification Workflow: Enforces a step‑by‑step process to identify, run, read, and verify commands before any status claim.
Error Prevention: Stops expressions of satisfaction or commit actions until evidence is verified, reducing false positives in testing, building, and linting.
Applicable Contexts: Ideal for software development pipelines, CI/CD checks, code reviews, and any task where correctness must be proven before progressing.

Quick Start

Ask the skill to run your test command and confirm the output before marking the task as 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 prevent false success claims in CI/CD pipelines before marking work complete?▼

You prevent false success claims by running verification commands and checking fresh output evidence, such as exit codes, before stating work is complete. This enforces a step-by-step process to identify, run, read, and verify commands.

What is the verification workflow for software testing and building?▼

The verification workflow for software testing and building requires executing designated commands, checking exit codes and output evidence, and only then allowing success claims. This stops premature expressions of satisfaction or commit actions.

How to verify linting and code review output before declaring a task done?▼

To verify linting and code review output before declaring a task done, run the designated command, read the fresh output evidence, and confirm the exit code. This prevents rework caused by unchecked assertions.

Why does my software development workflow allow commit actions without verification evidence?▼

Your workflow allows commit actions without verification evidence because it lacks a mechanism to block expressions of satisfaction until fresh output is verified. Enforcing command execution and exit code checks eliminates this dishonesty.

Does this verification process work with existing CI checks and status updates?▼

Yes, this verification process works with existing CI checks and status updates. It applies to any software development scenario where correctness must be proven before progressing, including testing, building, and linting pipelines.

When do I need to run verification commands before a completion status update?▼

You need to run verification commands before a completion status update whenever a task requires correctness to be proven. This ensures every completion statement is backed by fresh verification evidence, reducing false positives.