Verification Before Completion

Run verification commands and inspect outputs before declaring work complete.

4|Updated Nov 16, 2025

Search Tags:#testing #CI/CD #verification #evidence #quality-assurance #software-engineering #claims

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reputable teams require evidence before declaring work complete. This Skill enforces verifying results with explicit commands and fresh outputs.

Core Features & Use Cases

Verification Gate: A repeatable process that runs full verification commands and evaluates their outputs before declaring completion.
Evidence-Based Claims: Promotes asserting success only after outcomes are validated (tests, builds, checks, and QA feedback).
Use Case: Before merging a feature branch, run the verification suite, inspect exit codes and logs, and only mark the change as done when results are clean.

Quick Start

Run the built-in verification workflow to validate the latest changes and report the outcome.

Frequently Asked Questions about Verification Before Completion

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

FAQPage Schema

How do I automate verification of work evidence before claiming completion?▼

To automate verification of work evidence, you can enforce a verification gate that runs full commands, inspects outputs and exit codes, and only claims completion when results are clean. This ensures evidence-based validation prior to delivery.

What is evidence-based claiming in software engineering?▼

Evidence-based claiming in software engineering is the practice of asserting work success only after running full verification commands and validating fresh outputs like tests, builds, and QA checks.

How do I enforce a verification gate in my CI/CD pipeline?▼

You can enforce a verification gate in your CI/CD pipeline by automating the execution of full verification suites, inspecting logs and exit codes, and restricting completion claims until all outputs are validated as clean.

Can I use automated verification to check tests and builds before merging a feature branch?▼

Yes, you can use automated verification to check tests and builds before merging a feature branch by running the verification suite, inspecting the results, and only marking the change as done when outcomes are fully validated.

Does the verification workflow require any specific dependencies or components?▼

The verification workflow does not require any specific dependencies or components, allowing you to integrate the automated verification gate directly into your existing development, testing, and release workflows.