quantdev-verification

Enforce evidence-based verification commands before claiming task completion.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature claims of work completion, ensuring that all necessary verification steps are performed before any assertion of success, thereby maintaining code quality and project integrity.

Core Features & Use Cases

  • Mandatory Verification: Enforces running specific commands and checking their output before declaring a task done.
  • Evidence-Based Claims: Requires concrete proof (command output, test results) to support any statement of completion or correctness.
  • Use Case: Before committing code, you must run the relevant validation commands (e.g., tests, linters, specific track verifications) and present their output to confirm the work is truly complete and correct.

Quick Start

Run the verification commands and present their output before claiming your work is done.

Frequently Asked Questions about quantdev-verification

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

FAQPage Schema
How do I enforce mandatory verification commands before a pre-commit assertion?

An evidence-based workflow requires executing validation commands and reviewing their output before asserting task completion. This mechanism prevents premature success claims by demanding concrete proof, such as test results or linter output, to verify code changes before proceeding.

How do I implement evidence-based validation for CI/CD pipelines?

Implementing evidence-based validation for CI/CD pipelines involves requiring command outputs and test results as concrete proof before merging. This enforces rigorous pre-merge validation protocols, ensuring project integrity by verifying that all development stages meet strict quality criteria.

Does pre-commit verification work with different development tracks like bots and research?

Pre-commit verification works across all development tracks, including code changes, bots, and research. It applies strict evidence-based validation protocols universally, requiring specific command execution and output review before allowing any success assertions or completion claims in any track.

What is the best way to prevent premature claims of work completion in software engineering?

The best way to prevent premature claims of work completion is to enforce strict pre-merge validation protocols. By requiring developers to run verification commands and present their output as evidence, you ensure rigorous validation of code changes before any success is declared.

Why do I need to run verification commands before claiming a task is done?

You need to run verification commands before claiming a task is done to maintain code quality and project integrity. This requirement ensures that all necessary validation steps are performed and supported by concrete proof, preventing false assertions of correctness or completion.