verification-before-completion

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

Run verification commands and assert completion only with corroborating evidence.

Updated Aug 23, 2026

Ready to run

npx skills add https://github.com/chriscarterux/chris-claude-stack --skill verification-before-completion-chriscarterux

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates premature completion claims and false success reports that lead to broken trust, shipping bugs, and wasted rework time.

Core Features & Use Cases

Evidence-Based Validation: Requires running actual verification commands before any success claims
Quality Gate Enforcement: Prevents commits, PRs, and task completion without fresh proof
Trust Restoration: Replaces assumptions and confidence with concrete evidence
Use Case: Before claiming "tests pass" or "bug fixed," this Skill forces you to run the actual test command, verify zero failures, and provide the output as proof.

Quick Start

Use the verification-before-completion skill when you're about to say work is done. It will prompt you to run verification commands and provide evidence before making any completion claims.

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 tests pass before claiming work is complete?▼

Verification before completion requires running actual test commands, reading output, checking exit codes, and confirming zero failures. Only then can you claim success with corroborating evidence instead of assumptions.

Why should I run verification commands instead of assuming my code works?▼

Running fresh verification prevents false success reports that lead to broken trust, shipped bugs, and wasted rework. Evidence-based validation replaces confidence with concrete proof from actual test runs and build outputs.

What verification steps should happen before a PR or commit is complete?▼

Before completion, execute the full verification command—tests, builds, and linting—read all outputs, validate exit codes show success, count failures as zero, and provide output evidence. This enforces quality gates and prevents premature claims.

Can I skip verification if I'm confident the changes work?▼

No. Verification before completion eliminates premature claims by requiring actual command execution and proof. Confidence without evidence leads to bugs shipping; this Skill forces concrete validation before any success declaration.

How does verification prevent bugs from reaching production?▼

By requiring fresh verification evidence—test output, build logs, linting results—before claiming completion, this Skill acts as a quality gate. It blocks commits and PRs without proof, catching failures before they ship.