verification-before-completion

Verify completion claims by running commands and documenting output evidence.

Updated Mar 30, 2026

Search Tags:#documentation #qa #verification #evidence #process #software-testing #exit-code

Ready to run

npx skills add https://github.com/radenadri/skills-alena --skill verification-before-completion-radenadri

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claims of completion are often premature without explicit verification. This skill enforces evidence-based completion by requiring fresh verification outputs before asserting success.

Core Features & Use Cases

Enforces running verification commands and validating outputs before declaring completion.
Provides a gate-like workflow with required checks, exit-code verification, and evidence capture.
Applies across development, testing, and deployment pipelines to prevent false positives.

Quick Start

Run the official verification command in this response and attach its output as evidence before claiming completion.

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 software testing completion claims with fresh evidence?▼

Verifying software testing completion claims with fresh evidence requires running a full verification command and inspecting its outputs. This skill enforces evidence-based completion by validating exit codes and capturing command outputs before asserting success.

What is evidence-based verification in development pipelines?▼

Evidence-based verification in development pipelines is the practice of proving status claims with actual command outputs. It prevents false positives by requiring fresh verification runs and inspecting outputs before declaring a build successful or a bug fixed.

How do I prevent false positives in deployment pipelines?▼

Preventing false positives in deployment pipelines requires a gate-like workflow with mandatory checks. You must run verification commands, validate exit codes, and document the evidence before declaring completion to ensure claims are not premature.

Does this verification process work across development, testing, and deployment pipelines?▼

Yes, the verification process applies across development, testing, and deployment pipelines. It enforces running a full verification command, inspecting outputs and exit codes, and documenting evidence before declaring success in any pipeline stage.

Why does my automated build report success without command output evidence?▼

Automated builds report success without command output evidence when completion claims are premature without explicit verification. This skill enforces evidence-based completion by requiring fresh verification outputs before allowing a success assertion.