verification-before-completion

Require fresh verification evidence before claiming task completion.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents false “done/passing” claims by requiring fresh, evidence-based verification before you express completion.

Core Features & Use Cases

  • Evidence-first completion: Forces the sequence “run → inspect evidence → only then claim success,” reducing dishonest or accidental overstating of status.
  • Verification tiers for common stacks: Uses verify:full for implementer/QA workflows and verify:quick for reviewers, aligning effort with role.
  • Robust fallback when project scripts are missing: Still requires running the underlying lint/typecheck/test/build commands rather than relying on prior runs.
  • Use Case: Before merging or finishing a task, verify that linting, typechecking, tests, and (when applicable) build/coverage truly pass, then include the confirmation evidence in your final status.

Quick Start

Use this skill when you are about to report the work is complete: run the appropriate verification tier command for your project, confirm the success gate output, and only then state the result with the evidence line.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I prevent false completion claims before creating a PR or committing changes?

Code review verification gates require running lint, typecheck, and test commands to produce fresh evidence, inspecting the output for an all-gates-passed signal, and withholding success wording until that confirmation is present.

What's the best way to enforce build validation and release readiness in JS/TS and Python projects?

Enforce build validation by executing verification tiers like verify:full or verify:quick, which run the underlying lint, typecheck, test, and build commands to confirm release readiness before closing tasks.

How does CI verification work when project scripts are missing?

When project scripts are missing, CI verification uses a robust fallback that directly executes the underlying lint, typecheck, and test commands rather than relying on prior runs or cached results.

Do I need a verify.sh script to run quality gates on my code?

You do not need a verify.sh script to run quality gates; the system applies a robust fallback that directly executes required lint, typecheck, and test commands if the optional project script is absent.

What is the difference between verify:full and verify:quick tiers for software testing?

For software testing, verify:full is designed for implementer and QA workflows requiring comprehensive checks, while verify:quick is tailored for reviewers to align verification effort with their specific role.