verification

Name: verification
Availability: InStock
Author: djwmobley

Run verification commands and attach output evidence before declaring completion.

Updated Mar 18, 2026

Search Tags:#qa #verification #audit #builds #claims #tests #exit-code

Ready to run

npx skills add https://github.com/djwmobley/pipeline --skill verification-djwmobley

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/djwmobley/pipeline/tree/main/skills/verification
Command: npx skills add https://github.com/djwmobley/pipeline --skill verification-djwmobley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming completion without verification leads to dishonesty and inefficiency; this Skill enforces evidence-based claims by requiring fresh verification before you declare success.

Core Features & Use Cases

Enforces a verification gate before declaring completion.
Provides a repeatable process to run verification commands, read outputs, and validate results.
Use Case: auditors, QA, and CI pipelines rely on verifiable outputs to confirm success.

Quick Start

Run the verification command and attach the full output to your claim to ensure transparency.

Frequently Asked Questions about verification

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

FAQPage Schema

How do I enforce verification evidence before declaring a build successful?▼

Build verification requires running the full command, reviewing outputs, and checking exit codes before declaring success. You enforce evidence-based claims by attaching fresh logs to validate the build results transparently.

What is evidence-based verification in QA gates?▼

Evidence-based verification in QA gates ensures every completion claim is backed by fresh test outputs and exit codes. It prevents dishonesty by requiring auditors to run commands and validate verifiable results before confirming success.

How do I audit completion claims using exit codes and logs?▼

Auditing completion claims requires running the full verification command, capturing the output logs, and validating the exit codes. This process ensures that success claims are strictly backed by fresh verifiable evidence from the test run.

Can I use this verification process for CI pipeline testing?▼

Yes, CI pipelines rely on verifiable outputs to confirm success. The verification process applies directly to testing and QA gates by enforcing a verification step that requires fresh command outputs and exit codes before passing the build.

Why does claiming completion without verification lead to inefficiency?▼

Claiming completion without verification leads to inefficiency because it allows untested builds to pass QA gates. Enforcing a verification gate requires fresh evidence like outputs and exit codes, ensuring only honest and validated success claims proceed.