verification-before-completion

Require fresh command outputs and logs before completion claims.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/i0switch/yoyaku-tosho --skill verification-before-completion-i0switch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/i0switch/yoyaku-tosho/tree/main/.github/skills/verification-before-completion
Command: npx skills add https://github.com/i0switch/yoyaku-tosho --skill verification-before-completion-i0switch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Verification before completion ensures honesty by requiring fresh evidence before claiming success.

Core Features & Use Cases

  • Enforces a step-by-step verification gate before completion claims.
  • Suitable for CI, code reviews, and release workflows that demand verifiable results.
  • Helps teams maintain integrity by insisting on evidence and explicit checks before assertions.

Quick Start

Run the verification workflow on your latest build and report the exact command output and exit status.

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 evidence before claiming CI completion?

Enforce verification before completion by requiring explicit verification commands, evaluating command outputs and exit status, and gating completion claims on fresh evidence logs.

What is a verification gate in code review workflows?

A verification gate in code review workflows is a mandatory step-by-step check that requires explicit command outputs and logs before any success claim can be asserted.

How do I automate quality assurance checks with command outputs?

Automate quality assurance by configuring verification workflows that require explicit commands, evaluate the resulting outputs, and enforce results reporting before final assertions.

Does this verification workflow work with CI and release pipelines?

Yes, this verification workflow is suitable for CI, code reviews, and release pipelines that demand verifiable results and require fresh evidence before completion.

What's the best way to prove software testing claims with evidence?

The best way to prove software testing claims is to run a verification workflow on your latest build and report the exact command output and exit status as evidence.

When do I need verification before completion in software engineering?

You need verification before completion in software engineering whenever a workflow demands verifiable results, ensuring honesty by requiring fresh evidence before claiming success.