verification-before-completion

Run verification commands and report completion only with fresh evidence.

Updated Jan 20, 2026

Search Tags:#verification #build #evidence #quality-assurance #PR #CI #tests

Ready to run

npx skills add https://github.com/hitsumabushi334/KGpaper --skill verification-before-completion-hitsumabushi334

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces verification before any completion claim, preventing dishonest or premature statements about task status.

Core Features & Use Cases

Verification gate: Requires identifying, running, and reading verification commands to ensure claims are supported by fresh evidence.
Process discipline: Applies to code, PRs, CI checks, tests, and task handoffs; ensures progress updates are backed by verifiable results.
Governance example: Before merging a PR or marking work as done, run the appropriate checks and document the results as evidence.

Quick Start

Run the prescribed verification commands, inspect their outputs, and only then assert success. Record and present the evidence of verification.

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 claiming task completion in software development?▼

To enforce verification before claiming task completion, you must identify the appropriate verification command, run it, and read the full output to ensure progress updates are backed by fresh evidence. This process discipline prevents premature status claims.

What is the best way to require PR readiness evidence before merging?▼

The best way to require PR readiness evidence is to implement a verification gate that runs CI checks and tests, documents the results, and only reports success after inspecting the verifiable output. This prevents dishonest or premature completion statements.

How does a verification gate work for task handoffs?▼

A verification gate for task handoffs works by requiring the execution of verification commands and inspecting their full output before any success is reported. This ensures that all progress claims are strictly backed by fresh, verifiable results.

Do I need to run tests to mark a software development task as done?▼

Yes, you need to run tests or appropriate verification commands and read their full output before marking a software development task as done. You must record and present this evidence to support any claims of successful completion.

Why should I prevent premature completion claims in CI workflows?▼

You should prevent premature completion claims in CI workflows to ensure that progress updates and PR merges are strictly backed by fresh verification evidence. This governance practice maintains quality assurance by requiring verifiable results before any success is asserted.