skills.rest
tusosos
tusososCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run verification commands and assert completion only with fresh evidence.

Updated Apr 3, 2026
Search Tags:#testing#validation#verification#ci-cd#quality-assurance#code-review
One-click install
npx skills add https://github.com/tusosos/manus-knowledge-base --skill verification-before-completion-tusosos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/tusosos/manus-knowledge-base/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/tusosos/manus-knowledge-base --skill verification-before-completion-tusosos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification is dishonest, not efficient. The Iron Law requires fresh verification evidence before any success claim, ensuring accountability and traceability. If verification was not run, success claims must be withheld.

Core Features & Use Cases

  • Enforces a rigorous verification gate before any completion claim, reducing false positives.
  • Guides users through a 5-step verification process: IDENTIFY, RUN, READ, VERIFY, and CLAIM ONLY with evidence.
  • Useful for code reviews, PRs, deployments, and any scenario where audit trails and reproducible results matter.

Quick Start

Run the verification command, read its full output, and only then declare the result with evidence.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I enforce verification before claiming a code review is complete?▼

To enforce verification before completion, run the full validation command, interpret its output, and only claim success with fresh evidence. This process ensures accountability and reduces false positives during code reviews.

Why does claiming work is complete without validation cause issues in CI-CD?▼

Claiming completion without verification is dishonest and creates false positives. Enforcing an evidence-based verification gate ensures traceability and reproducible results across CI-CD pipelines before any success is asserted.

What is the best way to ensure quality assurance claims are backed by fresh evidence?▼

The best way to ensure quality assurance claims are backed by evidence is following a five-step process: IDENTIFY, RUN, READ, VERIFY, and CLAIM ONLY with proof. This guarantees every success assertion is traceable.

Can I use this verification process for both software deployments and pull requests?▼

Yes, you can use this verification process for deployments, pull requests, and code reviews. It applies evidence-based completion across various development workflows by requiring fresh verification results before asserting success.

What happens if testing verification was not run before a deployment success claim?▼

If testing verification was not run, success claims must be withheld. The Iron Law requires fresh verification evidence before any completion claim to maintain accountability and prevent unverified deployment assertions.

Related Skills

Explore More Software Engineering Skills→
edlngedlng
2

verification-before-completion

Run validation commands and review output logs before claiming task completion.

Community
Advanced
hanibalskhanibalsk
3

verification-before-completion

Run verification commands and require evidence before completion claims.

Community
Basic
Muath2000Muath2000

qa-architect

Design software quality assurance strategies and automated testing frameworks.

Community
Advanced
zcacereszcaceres
7

dead-code-analyzer

Detect dead code, duplicate logic, and circular dependencies with knip, jscpd, and madge.

Community
Advanced