verification-before-completion

Enforce verification commands and attach output evidence before task completion.

2|Updated Apr 20, 2026

Search Tags:#validation #qa #verification #evidence #process #guardrails #pull-request

Ready to run

npx skills add https://github.com/FelixBitSoul/contentCrew-AI --skill verification-before-completion-felixbitsoul

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/FelixBitSoul/contentCrew-AI/tree/main/.trae/skills/verification-before-completion
Command: npx skills add https://github.com/FelixBitSoul/contentCrew-AI --skill verification-before-completion-felixbitsoul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In many workflows, teams declare work done only after verification, but lack of verifiable evidence leads to inaccurate status reporting. This Skill provides a structured verification process to ensure there is observable proof before claiming completion.

Core Features & Use Cases

Automated verification workflow: enforces running the verification commands, parses outputs, and records evidence.
Applies to development and content workflows: ensures validation before submitting PRs, closing tasks, or delivering work.
Evidence-driven governance: provides auditable proof for status assertions and reduces rework.

Quick Start

在提交或创建 PR 之前，执行完整的验证命令并附上输出证据。

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 evidence-based verification before closing a pull request?▼

To enforce evidence-based verification before a pull request, you need an automated validation workflow that runs verification commands, parses test outputs, and attaches observable proof prior to marking any task as complete.

What is evidence-based completion verification in software development?▼

Evidence-based completion verification is a structured QA process requiring observable proof, such as passing test outputs and review records, to ensure accurate status reporting and reduce rework before claiming work is done.

How do I attach validation proof when submitting a PR or closing tasks?▼

You attach validation proof by running required verification commands, parsing their execution outputs, and recording the results as auditable evidence to support your status assertions for PR submission or task closure.

Does this verification process apply to content workflows or only software development?▼

This verification process applies to both software development and content workflows, ensuring required validation steps are completed and verified before delivering work, submitting pull requests, or closing tasks.

Why do I need guardrails for task validation and status reporting?▼

You need guardrails for task validation to prevent inaccurate status reporting, enforce the execution of verification commands, and ensure deterministic auditable proof exists before any work is marked as complete.