verification-before-completion

Verify completion claims across commits, PRs, builds, and deployments with fresh evidence.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Ab0umar/SRV100_Acc --skill verification-before-completion-ab0umar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Ab0umar/SRV100_Acc/tree/main/.codex/plugins/cache/openai-curated/superpowers/dc902811/skills/verification-before-completion
Command: npx skills add https://github.com/Ab0umar/SRV100_Acc --skill verification-before-completion-ab0umar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification before completion prevents claiming work is complete without fresh verification evidence, guarding against dishonesty and misrepresentation in release cycles.

Core Features & Use Cases

  • Enforces verification before any completion claim (code, tests, deployment)
  • Provides a repeatable checklist to capture and present evidence
  • Supports audit trails for PRs, builds, and releases

Quick Start

Run the full verification command, review the output, and only declare completion if the evidence confirms success

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 before claiming completion in a pull request?

Verify code changes before completion by executing the full verification workflow, capturing fresh output and exit status evidence. Only declare completion for commits, pull requests, builds, and deployments when the explicit evidence confirms success.

What is verification before completion in CI/CD release cycles?

Verification before completion is the process of requiring fresh evidence before declaring work done in CI/CD release cycles. It prevents dishonesty and misrepresentation by enforcing a repeatable checklist to verify code, tests, and deployments.

How do I capture verification evidence for builds and deployments?

Capture verification evidence by executing the full verification command across builds and deployments. Read the output and exit status, and report pass or fail with explicit evidence before declaring any completion claim.

What are the limitations of relying on verification evidence before completion?

The limitation of verification evidence is that it requires executing the full verification workflow manually for accurate results. It cannot confirm completion if the output and exit status evidence is missing or indicates failure.