skills.rest
SESELOVSKYDarian
SESELOVSKYDarianCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

verification-before-completion

Enforces running verification commands before claiming work is complete or passing.

Updated Mar 31, 2026
Search Tags:#code quality#testing#tdd#verification#evidence#build validation#completion claims
One-click install
npx skills add https://github.com/SESELOVSKYDarian/Vase --skill verification-before-completion-seselovskydarian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/SESELOVSKYDarian/Vase/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/SESELOVSKYDarian/Vase --skill verification-before-completion-seselovskydarian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers often claim work is done, tests pass, or bugs are fixed without actually running the verification commands, leading to broken code, lost trust, and wasted rework. This Skill enforces an evidence-first discipline so no completion claim is made without fresh command output. ## Core Features & Use Cases - Verification Gate: Defines a mandatory five-step gate (identify, run, read, verify, claim) before any success statement, commit, or PR. - Failure Pattern Catalog: Maps common claims (tests pass, build succeeds, bug fixed) to the exact evidence required and what does not count as proof. - Rationalization Blocking: Lists red-flag phrases and excuses ("should work", "just this once") that signal an unverified claim is about to be made. - Use Case: Before committing a bug fix, the agent runs the test suite, confirms zero failures in the output, and only then reports the fix as verified with the evidence attached. ## Quick Start Before claiming any task is complete, run the relevant verification command and report the actual output alongside your claim.

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 work is complete before committing code?▼

Identify the command that proves your claim, run it fresh and in full, read the entire output including exit code and failure counts, then make your claim only with that evidence attached. Never commit based on previous runs or assumptions.

What counts as evidence that tests pass?▼

Only the fresh output of the test command showing zero failures counts as evidence. Previous runs, partial checks, linter results, or confidence that the code should pass are explicitly not sufficient proof.

Can I trust a linter passing as proof the build works?▼

No, a linter passing does not verify compilation or build success. You must run the actual build command and confirm it exits with code 0 before claiming the build succeeds.

How do I verify a regression test actually works?▼

Use the red-green cycle: write the test, run it to confirm it passes with the fix, revert the fix and confirm the test fails, then restore the fix and confirm it passes again. A test that never fails proves nothing.

Should I trust a sub-agent's report that a task succeeded?▼

No, agent success reports must be independently verified. Check the version control diff to confirm the changes actually exist and match the claimed work before reporting completion.

Related Skills

Explore More Software Engineering Skills→
cookeyholdercookeyholder

test-driven-development

Write failing tests before implementation to enforce a red-green-refactor workflow.

Community
Intermediate
SeanChenRSeanChenR

verification-before-completion

Require fresh verification commands and output inspection before completion claims.

Community
Intermediate
aquariuscookaquariuscook

shift-left-testing

Integrate testing into requirements and design phases with TDD and CI/CD.

Community
Advanced
NealschNealsch

Forge-CI-CD-Pipeline-Execution

Designs CI/CD pipeline stages, gating policies, and failure triage procedures.

Community
Intermediate