verification-before-completion

Run verification commands and collect outputs before completion claims.

Updated Mar 20, 2026

Search Tags:#validation #verification #evidence #quality-assurance #development-workflow

Ready to run

npx skills add https://github.com/sixscripts-ai/ghostssh --skill verification-before-completion-sixscripts-ai

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification leads to dishonest reporting and wasted time. This Skill ensures every completion claim is backed by fresh verification evidence, reducing risk and rework.

Core Features & Use Cases

Verification gating: Run a verification command set to prove the status before committing or merging.
Evidence collection: Capture outputs, exit codes, and relevant artifacts to accompany status claims.
Audit-ready reporting: Produce a verifiable trail of results for reviews, CI gates, and governance.

Quick Start

Run the verification command to generate fresh evidence before making any completion claim.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I prevent premature completion claims in development workflows?▼

To prevent premature completion claims, enforce verification gating by running a command set to prove task status before committing or merging. This coordinates running verification commands and validates deterministic outputs to ensure work is fully complete.

What is verification gating and how does it support quality assurance?▼

Verification gating is the process of running a validation command set to prove task status before claiming completion. It supports quality assurance by enforcing strict validation against deterministic outputs and preventing unverified success declarations.

How do I collect evidence for audit-ready compliance reporting?▼

Collect evidence for audit-ready compliance reporting by capturing command outputs, exit codes, and relevant artifacts. This produces a verifiable trail of results for reviews, CI gates, and governance to meet risk and compliance requirements.

Can I use verification evidence collection for CI gate enforcement?▼

Yes, you can use verification evidence collection for CI gate enforcement. The process records fresh validation outputs and exit codes, producing an audit-ready trail of results that governance and CI gates can verify before merging changes.

Does verification before completion work without external dependencies?▼

Yes, verification before completion works without external dependencies. The Skill coordinates running validation commands and collecting outputs directly within your development workflow to enforce strict validation and record evidence independently.

What are the limitations of enforcing strict validation against deterministic outputs?▼

Strict validation against deterministic outputs requires commands to produce consistent, repeatable results. If your verification commands rely on non-deterministic outputs or external state, the validation may fail or produce inconsistent evidence for completion claims.