skills.rest
compozy
compozyOFFICIAL
Explore all skills by this author →
Website𝕏@compozyaiGitHub

verification-before-completion

Verify work claims with fresh evidence before declaring completion.

83|9|Updated May 6, 2026
Search Tags:#logs#verification#completion#evidence#builds#claims#tests
One-click install
npx skills add https://github.com/compozy/skeeper --skill verification-before-completion-compozy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/compozy/skeeper/tree/main/.agents/skills/verification-before-completion
Command: npx skills add https://github.com/compozy/skeeper --skill verification-before-completion-compozy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces honesty in progress reporting by requiring fresh verification evidence before any completion claim is made.

Core Features & Use Cases

  • Gate any completion claim behind a verified verification command, ensuring fresh output is produced and examined.
  • Applicable to code changes, builds, tests, and task deliveries where evidence is required to substantiate success.
  • Real-world use: before merging a feature branch, produce verification output and attach it to the PR as proof of readiness.

Quick Start

Run the verification command to generate fresh output and attach it as evidence before declaring completion.

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 code changes with fresh evidence before declaring completion?▼

Run a fresh verification command to generate new output, assess the results, and only then publish a final completion claim to ensure concrete evidence substantiates the readiness of your deliverables.

What does it mean to gate a completion claim behind verified evidence?▼

Gating a completion claim means a verification command must run and produce fresh output that is examined before any success is declared, enforcing honesty in progress reporting for code changes and task deliveries.

How do I attach verification logs to a pull request as proof of readiness?▼

Run the verification command to generate fresh logs and attach that output to the PR as evidence of readiness, proving code changes pass verification before the feature branch is merged.

Can I use this verification process for both builds and tests?▼

Yes, the verification process applies to code changes, builds, tests, and task deliveries, where any deliverable requiring verification artifacts to substantiate completion claims can be gated behind fresh evidence.

Why does my completion claim fail without fresh verification output?▼

Completion claims fail without fresh verification output because the process requires newly generated evidence to substantiate success, and stale or missing logs do not satisfy the requirement to run and assess a fresh verification.

Related Skills

Explore More Software Engineering Skills→
jagreehaljagreehal
3

verification-before-completion

Run verification commands and report outputs before completion claims.

Community
Intermediate
hanibalskhanibalsk
3

verification-before-completion

Run verification commands and require evidence before completion claims.

Community
Basic
growingiogrowingio
91

verification-before-completion

Run automated test commands and analyze output logs to validate code changes.

Official
Intermediate
elophantoelophanto
116

verification-before-completion

Execute verification commands and report pass/fail with evidence before completion.

Community
Advanced