verifying-completion

Run verification commands and report completion status with evidence.

3|Updated Jan 22, 2026

Search Tags:#verification #evidence #quality-assurance #verify #code-review #claims

Ready to run

npx skills add https://github.com/falconnt/windsurf-skills --skill verifying-completion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verifying-completion
Source: https://github.com/falconnt/windsurf-skills/tree/main/verifying-completion
Command: npx skills add https://github.com/falconnt/windsurf-skills --skill verifying-completion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that work is not declared complete without fresh verification evidence, preventing unverified success claims.

Core Features & Use Cases

Enforces evidence-based completion checks before commits or PRs.
Provides a repeatable verification process that can be applied across tasks.
Supports documenting results and linking to verification outputs.

Quick Start

Run the verification command(s) to generate fresh outputs and report the final status with concrete evidence.

Frequently Asked Questions about verifying-completion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify task completion with evidence before making a commit?▼

You can prevent unverified success claims by requiring fresh verification evidence before commits or pull requests, ensuring that validation commands are executed and their outputs are audited before any work is declared complete.

What is evidence-based verification for code review?▼

Evidence-based verification is a quality assurance process that prevents unverified success claims by requiring the execution of validation commands and a full audit of their results before declaring any code, document, or task complete.

Can I use this verification process for both code and documents?▼

Yes, this validation process applies to code, documents, or tasks ending in commits or pull requests, requiring you to identify and execute verification commands in full and audit their results before reporting completion.

How do I enforce quality assurance checks before a pull request?▼

You can enforce quality assurance by applying a repeatable verification process that requires running validation commands, auditing the results, and documenting the final status with concrete evidence before submitting a pull request.

What are the limitations of relying on claims without fresh verification outputs?▼

Relying on claims without fresh verification outputs risks declaring work complete without proof, which this validation process prevents by mandating that verification commands are executed and their results audited before any success is claimed.