verification

Enforce running tests, builds, and linters before declaring task completion.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/Veraticus/gambit --skill verification-veraticus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/Veraticus/gambit/tree/main/skills/verification
Command: npx skills add https://github.com/Veraticus/gambit --skill verification-veraticus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures that any claim of task completion or success is backed by fresh verification results, preventing premature or unverified assertions.

Core Features & Use Cases

  • Enforce verification rituals: require running tests, builds, linters, and any other defined checks before declaring completion.
  • Quality assurance discipline: provides a formal gate to ensure evidence is reviewed and recorded.
  • Use Case: when delivering software changes, you verify that tests pass and build succeeds before merging.

Quick Start

Run the verification commands relevant to your project (e.g., tests, build) and report the results before marking a task complete.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I enforce running tests and builds before declaring a coding task complete?

To enforce task completion verification, you must run fresh verification commands like tests, builds, and linters, then present conclusive results before declaring success. This prevents premature or unverified assertions in software engineering.

What is evidence-backed verification in quality assurance?

Evidence-backed verification in quality assurance is a formal gate requiring fresh test, build, and lint results to be reviewed and recorded before any task completion claim is accepted.

How do I stop premature task completion claims in software development?

To stop premature task completion claims, apply a verification ritual that requires running the full suite of quality checks and presenting conclusive evidence before a task is marked as done.

Do I need specific testing frameworks to enforce verification rituals?

No specific testing frameworks are required. You run the verification commands relevant to your project, such as your existing tests, builds, and linters, and report the results before marking a task complete.

What's the best way to verify software changes before merging?

The best way to verify software changes before merging is to require running full verification commands across the project, ensuring all tests pass and builds succeed, then presenting that evidence as proof of completion.

When do I need to apply task completion verification?

You need to apply task completion verification when delivering software changes that require tests, builds, linters, and quality checks, ensuring evidence is reviewed before success is declared.