verification-before-completion

Enforce a verification gate with fresh test results before claiming completion.

58|6|Updated Dec 23, 2025

Search Tags:#automation #verification #completion #evidence #quality-assurance #pr-checks

Ready to run

npx skills add https://github.com/Matt-Aurora-Ventures/Jarvis --skill verification-before-completion-matt-aurora-ventures

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Matt-Aurora-Ventures/Jarvis/tree/main/.windsurf/skills/verification-before-completion
Command: npx skills add https://github.com/Matt-Aurora-Ventures/Jarvis --skill verification-before-completion-matt-aurora-ventures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming completion without verification leads to misinformation and unreliable results. This Skill ensures evidence-based claims by enforcing a structured verification process.

Core Features & Use Cases

Enforces a strict verification gate before declaring success, using fresh outputs and evidence.
Guides teams through a repeatable workflow: identify command, run verification, read results, verify, and commit with evidence.
Use Case: before merging a PR, run verification commands and attach evidence to support completion status.

Quick Start

Run the verification command, review the full output, and only claim completion if verification passes.

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 a pull request is complete?▼

To enforce verification before claiming a pull request is complete, run full verification commands, review the fresh output logs, and only declare success if the results pass. This structured process prevents unverified success by requiring evidence-based assertions.

What is the step-by-step process for software deployment verification?▼

The step-by-step process for software deployment verification involves identifying the command, running the full verification, reading the outputs, verifying the results, and only then claiming completion with all evidence attached. This enforces a strict quality-assurance gate.

How do I attach fresh test results as evidence for development milestones?▼

You attach fresh test results as evidence for development milestones by running the required verification commands and capturing the output logs immediately before claiming completion. This ensures all assertions are supported by newly generated proof rather than assumed success.

Why does claiming completion without verification lead to unreliable software results?▼

Claiming completion without verification leads to unreliable software results because it allows unproven outcomes to propagate through deployment checks. Enforcing a verification gate with fresh outputs prevents misinformation by ensuring every success claim is backed by concrete logs.

Can I use automated checks for pull requests without attaching evidence?▼

You cannot use automated checks for pull requests without attaching evidence if you follow this verification process. It strictly enforces that all PR-checks must be run, outputs read, and results verified with fresh logs before any completion status is asserted.