verification-before-completion

Enforce verified evidence before declaring PR, merge, or release completion.

Updated Jun 6, 2026

Search Tags:#validation #verification #evidence #quality-assurance #code-review #release-readiness #pr-process

Ready to run

npx skills add https://github.com/pcsensor/serial --skill verification-before-completion-pcsensor

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

在宣称工作完成、已修复或测试通过之前，要求进行可验证的证明，确保所有断言都有实证支撑，避免不透明的声称与失效的承诺。

Core Features & Use Cases

强制执行验证流程：在提交 PR、合并或发布前运行验证命令并记录输出。
提供可复用的门控逻辑与证据记录方法，确保结论可追溯。
使用场景：在软件发布前进行回归测试、在任务完成时生成可验证的结果证据。

Quick Start

运行完整的验证流程并生成证据来证明当前状态符合要求。

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 code release readiness?▼

To enforce verification before declaring code release readiness, run validation commands and analyze complete outputs to generate auditable proof. This prevents declaring completion or test success without validated evidence, ensuring all assertions have empirical support across PR submissions and merges.

What is the best way to prevent unverified PR submissions in software engineering?▼

The best way to prevent unverified PR submissions is to enforce a gatekeeping logic that mandates running verification commands and recording outputs. This ensures verifiable outcomes and provides traceable evidence before any merge or release readiness status is officially declared.

How does evidence-based validation work for task completion?▼

Evidence-based validation for task completion works by executing verification commands and analyzing their complete outputs to produce auditable proof. This mechanism ensures that every status claim is backed by empirical data, preventing opaque assertions and broken promises during software releases.

Can I use automated validation to generate proof for regression testing?▼

Yes, you can use automated validation to generate proof for regression testing. The process runs complete verification workflows and records the command outputs as evidence, proving that the current state meets the required release readiness criteria before task completion is declared.

Why does requiring verified evidence improve quality assurance?▼

Requiring verified evidence improves quality assurance by eliminating opaque status claims and broken promises. It forces teams to run verification commands and analyze complete outputs, ensuring that every assertion regarding test success or bug fixes is fully supported by auditable empirical data.