verification-before-completion

Run exact verification commands and inspect outputs before declaring work complete.

Updated Aug 27, 2026

Search Tags:#testing #tdd #verification #code-quality #vcs #developer-workflow #ci

Ready to run

npx skills add https://github.com/zephyrflow97/cadence --skill verification-before-completion-zephyrflow97

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents false or premature completion claims by enforcing that the exact verification commands are run and their outputs examined before any assertion of success, completion, or readiness is made.

Core Features & Use Cases

Verification Gate: A stepwise protocol to identify the proving command, run it fresh, read full output and exit codes, and only then state success.
Pre-commit / Pre-PR Enforcement: Use when about to commit, create a PR, finish a task, or move to the next step to ensure tests, builds, and linters are genuinely passing.
Agent Oversight: Validate agent-reported success by checking VCS diffs and running the proving commands yourself to produce independent evidence.
Use case: Before merging a feature branch, run the full test suite and build, attach the outputs and exit codes, and only then declare the branch ready.

Quick Start

Run the verification command for the task, read the full output and exit code, and report the evidence before claiming success.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema

How do I verify code changes before claiming a task is complete?▼

To verify code changes before completion, run the exact verification commands like tests or builds, inspect their full outputs and exit codes, and attach the evidence before declaring the task successful.

What is a verification gate in a developer workflow?▼

A verification gate is a stepwise protocol requiring you to run a fresh proving command, read its full output and exit code, and only then state success, preventing premature completion claims in your developer workflow.

How do I validate agent-reported success in CI pipelines?▼

Validate agent-reported success by checking VCS diffs and independently running the exact verification commands to produce fresh execution evidence, ensuring you do not rely on unproven agent assertions of task completion.

When do I need to enforce pre-commit and pre-PR verification?▼

You need to enforce pre-commit and pre-PR verification when about to commit, create a pull request, finish a task, or move to the next step, ensuring your tests, builds, and linters are genuinely passing.

Can I use this verification protocol for local TDD and code quality checks?▼

Yes, you can use this verification protocol for local TDD and code quality checks by applying it whenever you finish a step, requiring fresh execution of linters and test suites with attached output evidence before any success statements.