skills.rest
handsomelong922
handsomelong922COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run verification commands and report results with evidence before completion claims.

Updated Apr 3, 2026
Search Tags:#verification#build#evidence#code-review#gating#ci#quality-control
One-click install
npx skills add https://github.com/handsomelong922/my-codex-skills --skill verification-before-completion-handsomelong922
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/handsomelong922/my-codex-skills/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/handsomelong922/my-codex-skills --skill verification-before-completion-handsomelong922

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification is dishonesty, not efficiency. Core principle: Evidence before claims, always. Violating the letter of this rule is violating the spirit of this rule.

Core Features & Use Cases

  • Enforce completion claims only after running verifications and inspecting fresh outputs.
  • Provide a structured gate function: identify, run, read, verify, and only then claim.
  • Improve auditability and reduce risk of premature releases or PR acceptance.

Quick Start

Run the verification command, inspect the full output, and report the final 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 enforce verification evidence before claiming a build is complete in CI?▼

Enforce verification evidence by requiring a fresh build output before any success claim. This ensures completion statements are backed by parsed command results, improving auditability and reducing premature releases.

What is the best way to gate code reviews on passing tests and builds?▼

Gating code reviews requires running verification commands, inspecting full outputs, and reporting final status with evidence. This structured gate function prevents dishonest completion claims and reduces PR acceptance risk.

How do I prevent premature release claims without running verification commands?▼

Preventing premature releases requires running verification commands and inspecting fresh outputs before any success claim. Claiming completion without this verification evidence violates core quality-control gating principles in CI environments.

How does requiring fresh verification evidence improve software quality control?▼

Requiring fresh verification evidence improves quality control by enforcing a structured gate: identify, run, read, verify, and only then claim. This ensures all success claims in software development workflows are backed by parsed command outputs.

Can I use verification gating for both tests and code reviews across CI environments?▼

Verification gating applies to software development workflows including tests, builds, and code reviews across CI environments. It requires running a verification command, parsing full command outputs, and reporting results with evidence before claiming completion.

Related Skills

Explore More Software Engineering Skills→
DFly7DFly7

verification-before-completion

Run full verification commands and attach output evidence before claiming success.

Community
Intermediate
shmily1012shmily1012
1

verification-before-completion

Requires fresh evidence from verification commands before allowing completion claims.

Community
Advanced
baleen37baleen37
10

verification-before-completion

Run and confirm verification commands before claiming work completion.

Community
Basic
jagreehaljagreehal
3

verification-before-completion

Run verification commands and report outputs before completion claims.

Community
Intermediate