skills.rest
victorqnguyen
victorqnguyenCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Require fresh verification command output before declaring task completion.

Updated Aug 23, 2026
Search Tags:#testing#verification#evidence#quality-assurance#code-review#claims#gate
One-click install
npx skills add https://github.com/victorqnguyen/victors-architecture --skill verification-before-completion-victorqnguyen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/victorqnguyen/victors-architecture/tree/main/packages/core/skills/verification-before-completion
Command: npx skills add https://github.com/victorqnguyen/victors-architecture --skill verification-before-completion-victorqnguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claimed task completion is often asserted without fresh verification evidence, risking undetected errors and low trust. This Skill enforces evidence-first completion by requiring explicit verification before declaring success.

Core Features & Use Cases

  • Enforces an evidence-based gate for completion across tests, linting, builds, and reviews.
  • Guides users to identify the exact verification command, run it fully, and validate the resulting output and exit status.
  • Applies to collaborative workflows where PRs, releases, or task handoffs must be backed by verifiable results.

Quick Start

Run the full verification command for the current task and report the exact output as evidence before declaring 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 prevent false task completion claims without running verification commands?▼

To prevent false completion claims, enforce an evidence-based gate requiring fresh verification commands like tests, linters, or builds to run fully and validate outputs before reporting success.

What is an evidence-based gate for code review and testing?▼

An evidence-based gate for testing and code review mandates executing verification commands, validating exit codes, and reading outputs to ensure progress is backed by fresh, verifiable results.

How do I require test execution evidence before declaring task success?▼

Requiring test execution evidence involves identifying the exact verification command, running it fully, checking the exit status, and reporting the exact output as proof before declaring task success.

Can I use automated verification gates for collaborative workflows and PR handoffs?▼

Yes, you can apply automated verification gates to collaborative workflows where pull requests, releases, or task handoffs must be explicitly backed by fresh verification evidence.

What happens if my build or linting verification fails before task completion?▼

If build or linting verification fails, the evidence-based gate prevents declaring success, ensuring undetected errors are caught by validating exit codes and outputs before progress is allowed.

When do I need fresh verification evidence for quality assurance?▼

You need fresh verification evidence for quality assurance whenever claiming task completion in verification-driven workflows, ensuring progress is allowed only after validating command outputs and exit codes.

Related Skills

Explore More Software Engineering Skills→
mrkhachaturovmrkhachaturov

verification-before-completion

Runs a verification flow before allowing work to be marked complete.

Community
Advanced
nyldnnyldn
4.0k

skill-verify

Enforce an evidence gate before declaring completion in software workflows.

Community
Advanced
DevelopersGlobalDevelopersGlobal
65

ci-cd-pipelines

Automate CI/CD pipelines with quality gates and deployment processes.

Official
Advanced
danieldekaydanieldekay
1

verification-before-completion

Enforce evidence-backed verification of tests, linting, and builds before completion.

Community
Advanced