skills.rest
Ehrax
EhraxCOMMUNITY
Explore all skills by this author →
𝕏@0xEhraxGitHub

verification-before-completion

Verify completion claims with fresh command outputs before reporting success.

Updated Feb 11, 2016
Search Tags:#testing#verification#quality#evidence#process#claim
One-click install
npx skills add https://github.com/Ehrax/dotfiles --skill verification-before-completion-ehrax
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Ehrax/dotfiles/tree/main/configs/agents/skills/verification-before-completion
Command: npx skills add https://github.com/Ehrax/dotfiles --skill verification-before-completion-ehrax

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification is dishonesty, not efficiency. The core principle is that evidence should precede any claim of completion.

Core Features & Use Cases

  • Enforces a formal, step-by-step verification workflow: identify the proving command, run it fresh, read the output, verify against criteria, and only then claim success.
  • Improves integrity in software builds, tests, code reviews, and release readiness by preventing premature completion.
  • Typical use cases include validating feature readiness before merging, confirming bug fixes with verifiable outputs, and ensuring compliance of CI results with acceptance criteria.

Quick Start

Execute the verification steps for your current task and attach the complete command outputs before making any completion claim.

Frequently Asked Questions about verification-before-completion

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

FAQPage Schema
How do I verify build and test results before claiming a task is complete?▼

To verify results before claiming completion, you must identify a proving command, execute it fresh, read the full output, and validate it against predefined criteria. Only claim success after confirming the evidence matches your acceptance criteria.

Why does claiming work is done without verification cause problems in software engineering?▼

Claiming completion without verification introduces dishonesty into software engineering processes. Enforcing a formal, step-by-step verification workflow prevents premature completion claims and ensures integrity in builds, tests, and release readiness.

What is the best way to enforce evidence before a feature merge or release step?▼

The best way to enforce evidence before a release step is requiring explicit verification commands and attaching their complete outputs. This process ensures compliance with acceptance criteria before any completion claim is made.

Can I use a formal verification process for code reviews and bug fixes?▼

Yes, you can apply this verification process to code reviews and bug fixes. It guides you through identifying testing commands, executing them, and confirming fresh outputs against predefined criteria to validate readiness honestly.

Do I need to attach full command outputs when validating feature readiness?▼

Yes, you need to attach full command outputs when validating feature readiness. The verification workflow requires explicit verification steps and complete execution results to prove that outputs meet predefined quality criteria.

Related Skills

Explore More Software Engineering Skills→
HaRu-LLCHaRu-LLC

quality-plan

Define quality objectives, metrics, QA activities, and acceptance criteria for a project.

Community
Intermediate
ibalasiteibalasite

land-and-deploy

Merge pull requests, wait for CI, and verify production health via canary checks.

Community
Advanced
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
Chang-Shih-YungChang-Shih-Yung

health

Aggregate type checker, linter, and test results into a 0-10 composite score.

Community
Advanced