verification

Require verification command execution and output before declaring task completion.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill ensures that all claims of completion, success, or correctness are backed by verifiable evidence, preventing false positives and ensuring robust development practices.

Core Features & Use Cases

  • Mandatory Verification: Enforces running specific commands (tests, builds, linters) before any completion claim.
  • Evidence-Based Claims: Requires explicit output and results from verification commands to support any assertion of success.
  • Use Case: Before merging a code change, you must run the test suite and present the output showing zero failures, confirming the fix did not introduce regressions.

Quick Start

Use the verification skill to confirm that all tests pass by running the project's test command and showing the output.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I enforce evidence-based validation before claiming a software task is complete?

To prevent false positives during software development, enforce mandatory verification by running specific commands like test suites or linters before claiming task completion. You must present the explicit command output and results as evidence to support any assertion of code correctness or success.

How do I verify code correctness and ensure tests pass before merging a change?

You verify code correctness by running the project's test command and presenting the output showing zero failures. This validation step confirms that a code change or fix did not introduce regressions, satisfying requirements for test passing, build success, and individual criterion verification.

What is the best way to require test output and build success evidence in a development workflow?

The best way to require test output and build success evidence is to mandate the execution of verification commands and present their explicit results. This enforces evidence-based claims for task completion, ensuring robust development practices by preventing false positives through rigorous validation.

Can I use command output to validate individual criterion completion for software projects?

Yes, you can use command output to validate individual criterion completion by running specific verification commands and presenting their results. This enforces evidence-based claims by requiring explicit output to satisfy requirements for test passing, build success, and individual criterion verification.

Why do I need to run linters and verification commands before declaring code correctness?

You need to run linters and verification commands before declaring code correctness to prevent false positives and ensure robust development practices. This mandatory evidence-based validation requires explicit output and results from verification commands to support any assertion of task completion or success.