verification-before-completion

Run verification commands and record outputs to justify completion claims.

Updated Jul 8, 2022

Search Tags:#verification #evidence #best-practices #quality-assurance #code-review #pull-request

Ready to run

npx skills add https://github.com/limaon/dotfiles --skill verification-before-completion-limaon

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/limaon/dotfiles/tree/main/.config/opencode/skills/verification-before-completion
Command: npx skills add https://github.com/limaon/dotfiles --skill verification-before-completion-limaon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces evidence-based completion by preventing premature completion claims and ensuring fresh verification before PRs, releases, or sign-offs.

Core Features & Use Cases

Enforces running verification commands prior to commits, merges, or releases.
Captures and records command outputs for auditability and accountability.
Guides users through identifying the verification command, executing it fully, and interpreting results to justify the status.

Quick Start

Identify the verification command that proves completion (e.g., test suite, build, lint).
Run the full command set freshly and collect all outputs.
Review exit codes and outputs, document any failures, and report the actual status 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 back code completion claims with fresh verification evidence?▼

To back code completion claims with fresh verification evidence, identify a verification command like a test suite or build, execute it fully, and interpret the outputs to justify the completion status.

What is evidence-based completion in software development?▼

Evidence-based completion is a workflow mechanism that prevents premature completion claims by ensuring fresh verification command outputs are captured and recorded before pull requests, merges, or releases.

How do I enforce running verification commands prior to commits?▼

To enforce running verification commands prior to commits, identify the command that proves completion, run the full set freshly, review exit codes, document failures, and report the actual status with evidence.

Does evidence-based completion apply to code reviews and pull requests?▼

Yes, evidence-based completion applies directly to code reviews and pull requests by guiding users to execute verification commands fully, read outputs, and verify that any status claim is supported by fresh evidence.

What is the best way to prevent premature completion claims during releases?▼

The best way to prevent premature completion claims during releases is to enforce evidence-based completion by running test suites or builds freshly, capturing outputs for auditability, and justifying statuses with actual results.

Do I need specific test frameworks to verify completion claims?▼

No specific test frameworks are required. You can use any existing test suite, build, or lint command as your verification command, provided you execute it fully and interpret the outputs to justify the status.