verification-before-completion

Enforce verification commands and evidence-based completion claims in development workflows.

7|1|Updated Feb 14, 2026

Search Tags:#verification #evidence #quality-assurance #code-review #continuous-integration #build-verification

Ready to run

npx skills add https://github.com/fratilanico/apex-os-bad-boy --skill verification-before-completion-fratilanico

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/fratilanico/apex-os-bad-boy/tree/main/verification-before-completion
Command: npx skills add https://github.com/fratilanico/apex-os-bad-boy --skill verification-before-completion-fratilanico

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before declaring work complete, teams risk shipping unverified results. This Skill enforces explicit verification commands and evidence-based claims to prevent misstatements.

Core Features & Use Cases

Enforces a formal verification gate before any success claim.
Guides collection of verification outputs (commands, exit codes, logs) and evidence for PRs and releases.
Provides a repeatable workflow that reduces risk of unverified changes entering production.

Quick Start

Invoke the verification gate on your current task and attach the fresh outputs as evidence before reporting 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 enforce verification before declaring a pull request complete?▼

To enforce verification before PR completion, apply a formal gate that requires running verification commands, analyzing fresh outputs, and reporting evidence-based results to stakeholders before any success claim is declared.

What is evidence-based build verification in continuous integration?▼

Evidence-based build verification in continuous integration is the process of collecting fresh command outputs, exit codes, and logs to validate that code changes are fully tested before entering production workflows.

How do I collect verification evidence for code review cycles?▼

Collect verification evidence for code review cycles by executing verification commands, capturing exit codes and logs, and attaching these fresh outputs to your PR to prove the changes work as intended.

Does this verification gate work with existing continuous integration workflows?▼

Yes, the verification gate integrates across existing development workflows and continuous integration PR cycles by identifying unverified completion claims and enforcing fresh verification outputs before final declaration.

What is the best way to prevent unverified changes from entering production?▼

The best way to prevent unverified changes entering production is enforcing a repeatable verification workflow that requires fresh command outputs and evidence-based claims before any work is declared complete.