verification-before-completion

Run fresh verification commands and capture outputs before claiming completion.

9|2|Updated Mar 12, 2026

Search Tags:#testing #verification #safety #governance #code-quality #best-practices #quality-assurance

Ready to run

npx skills add https://github.com/iclinic/afyapowers --skill verification-before-completion-iclinic

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work as complete without verification leads to unverified quality, hidden defects, and risky releases. This Skill enforces an evidence-first approach to ensure honesty and traceability in development workflows.

Core Features & Use Cases

Enforces an evidence-before-claim policy for all completion statuses.
Guides users through running fresh verification commands and validating outputs.
Provides auditable gates for PRs, builds, and releases to prevent premature success claims.

Quick Start

Run the verification command on your current work and report the fresh results.

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 changes before claiming a task is complete?▼

To verify code changes before claiming completion, you must run a fresh verification command, capture its outputs and exit codes, and validate the results before asserting success. This enforces an evidence-first approach ensuring traceability and preventing risky releases.

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

An evidence-first approach to quality assurance requires running verification tools to capture actual outputs and exit codes before reporting any completion status. It solves the problem of unverified quality and hidden defects by enforcing auditable gates for builds and PRs.

How do I get auditable evidence for a pull request or feature build?▼

To get auditable evidence for a pull request or feature build, run a fresh verification command on your current work and report the captured outputs and exit codes. This provides the traceable validation needed to prevent premature success claims during releases.

Can I use automated verification gates for release governance?▼

Yes, you can use automated verification gates for release governance by requiring fresh verification commands to run and validate results before completion is asserted. This provides auditable gates that enforce honesty and traceability across your development workflow.

Why does claiming completion without verification lead to hidden defects?▼

Claiming completion without verification leads to hidden defects because no fresh verification command is run to capture outputs and validate results. This bypasses evidence-first quality assurance, allowing unverified code changes to create risky releases with zero auditable traceability.

What's the best way to enforce a completion verification policy for code quality?▼

The best way to enforce a completion verification policy for code quality is to require running a fresh verification tool, capturing its outputs and exit codes, and validating the results before any success is claimed. This evidence-first approach ensures auditable gates for PRs and builds.