verification-before-completion

Name: verification-before-completion
Availability: InStock
Author: brmatola

Enforce fresh verification evidence before reporting task completion.

Updated Jan 17, 2026

Search Tags:#verification #build #evidence #quality-assurance #lint #CI #tests

Ready to run

npx skills add https://github.com/brmatola/gremlins --skill verification-before-completion-brmatola

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures you never claim work is complete without fresh verification evidence, preventing dishonest status updates and guaranteeing verifiable results.

Core Features & Use Cases

Enforces a repeatable verification workflow: identify the verification command, run it fully, and evaluate the output.
Applies to software development, QA, and operational tasks where completion claims require concrete evidence.
Use Case: before merging a PR, run the verification suite and only declare success if all checks pass with clear evidence.

Quick Start

Run the verification workflow for the current task: identify the verification command, execute it fully, review the output, and report the final status with evidence.

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 evidence before claiming a task is complete?▼

To enforce verification evidence before completion, you must run the full verification command, evaluate its output, and report the final status only with concrete evidence of the results.

What is the best way to prevent premature completion claims in a CI workflow?▼

The best way to prevent premature completion claims in a CI workflow is to apply a repeatable verification process that requires fresh evidence from your tests and lint checks before success is declared.

How do I verify QA checks before merging a PR?▼

To verify QA checks before merging a PR, identify your verification suite, run it fully to generate concrete evidence, and declare success only if all checks pass with clear output.

Can I use this to enforce a repeatable verification workflow for software development?▼

Yes, you can use this to enforce a repeatable verification workflow for software development by ensuring you identify the verification command, execute it fully, and evaluate the output before reporting status.

Why do I need fresh verification evidence for quality assurance tasks?▼

You need fresh verification evidence for quality assurance tasks to prevent dishonest status updates and guarantee verifiable results, ensuring work is never claimed complete without running the full verification suite.