Verification Before Completion

Name: Verification Before Completion
Availability: InStock
Author: levanminhduc

Run verification commands and analyze exit codes before reporting completion.

Updated Jul 23, 2025

Search Tags:#verification #evidence #quality-assurance #claims #gate

Ready to run

npx skills add https://github.com/levanminhduc/LuongHoaThoNew --skill verification-before-completion-levanminhduc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Verification Before Completion
Source: https://github.com/levanminhduc/LuongHoaThoNew/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/levanminhduc/LuongHoaThoNew --skill verification-before-completion-levanminhduc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work as complete without verification can lead to false confidence and quality issues. This skill enforces a disciplined, evidence-based approach to verify results before declaring success.

Core Features & Use Cases

Verification Gate: A step-by-step approach to prove completion with fresh results
Evidence-based Claims: Requires verifiable outputs before status updates
Quality Assurance: Reduces risk of omissions and misstatements

Quick Start

Run the verification workflow described in this skill to confirm outputs before making any completion claims, e.g., run the exact verification commands outlined in this guide.

Frequently Asked Questions about Verification Before Completion

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

FAQPage Schema

Why should I run verification commands before claiming completion?▼

Verification commands confirm that work is actually complete by producing fresh evidence—exit codes, test results, and build outputs. Without running them, claims can mask incomplete work, failing tests, or lint errors that weren't caught, creating false confidence and quality gaps.

How do I verify my code changes before declaring them done?▼

Execute the full verification workflow: run your build command, test suite, and lint checks. Analyze exit codes and output for errors. Report completion only when all verification steps pass and produce clean results—never skip or assume success.

What verification steps should I run across different codebases?▼

Verification applies universally: run the build command for compilation errors, execute the test suite for failures, and run lint checks for code quality issues. Each step must complete successfully with zero errors before you can claim the task is done.

Can verification prevent quality issues in my workflow?▼

Yes. Verification gates catch omissions, misstatements, and failures before you report status. By enforcing evidence-based claims backed by fresh command outputs, it reduces risk of shipping incomplete or broken work.

What happens if I skip verification and claim completion anyway?▼

Skipping verification means undiscovered failures—broken builds, failing tests, or lint violations—reach downstream stages. This creates rework, delays, and eroded confidence in status reports. Verification ensures claims match reality.