Verification Before Completion

Run verification commands and report outputs, exit codes, and failures before completion.

Updated Jan 28, 2026

Search Tags:#automation #testing #validation #verification #quality-assurance #code-review #assertion

Ready to run

npx skills add https://github.com/brixtonpham/claude-config --skill verification-before-completion-brixtonpham

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming completion without proper verification leads to inflated metrics and unreliable outcomes. This skill enforces an evidence-first approach to confirm results before declaring work finished.

Core Features & Use Cases

Enforces a 5-step verification process: identify, run, read, verify, and only then claim.
Ensures transparent reporting of actual status with evidence in every completion.
Use cases include software builds, test runs, code reviews, QA checks, and documentation approvals where verification is mandatory.

Quick Start

Instruct the agent to run the full verification workflow and report the validated status before any completion claim.

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 builds and test runs before claiming task completion?▼

Run explicit verification commands and collect fresh evidence like exit codes to verify software builds and test runs. This protocol ensures outcomes are confirmed with a transparent report detailing actual outputs and failures before declaring work finished.

What is an evidence-first approach to software quality assurance?▼

Evidence-first quality assurance enforces a 5-step verification process: identify, run, read, verify, and claim. It solves inflated metrics by requiring transparent reporting of actual status with verifiable evidence in every completion claim.

How do I automate validation checks for code reviews and QA tasks?▼

Automate validation for code reviews and QA tasks by applying a verification protocol across reviews, builds, and tests. Instruct the agent to run the full workflow and report the validated status based on actual exit codes and outputs before completion.

Does this verification protocol work for documentation approvals?▼

Yes, the verification protocol works for documentation approvals where verification is mandatory. It applies the same 5-step process to generate a transparent report detailing outputs and any failures to determine the actual status before completion.

Why does claiming completion without validation lead to unreliable outcomes?▼

Claiming completion without verification leads to unreliable outcomes because it inflates metrics with unconfirmed results. Enforcing an evidence-first approach ensures transparent reporting of actual status with verifiable evidence in every completion claim.

What is the best way to generate transparent reports for test automation?▼

Generate transparent reports for test automation by running explicit verification commands and collecting fresh evidence. This protocol details outputs, exit codes, and any failures to determine the actual validated status before claiming completion.