skills.rest
rakaadi
rakaadiCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Enforce evidence-based verification before declaring completion in release workflows.

1|Updated Jan 10, 2026
Search Tags:#verification#observability#evidence#release-management#ci-cd#quality-assurance#claims
One-click install
npx skills add https://github.com/rakaadi/agent-kit --skill verification-before-completion-rakaadi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/rakaadi/agent-kit/tree/main/skills/verfication-before-completion
Command: npx skills add https://github.com/rakaadi/agent-kit --skill verification-before-completion-rakaadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents claiming work is complete without fresh verification, ensuring evidence-based status updates.

Core Features & Use Cases

  • Enforces a formal verification flow before declaring completion.
  • Captures and analyzes command outputs to substantiate success claims.
  • Use Case: release readiness, PR closure, and QA sign-off require verifiable evidence.

Quick Start

Run the verification sequence before any merge or release to gather verifiable outputs and 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 evidence-based verification before claiming a software release is complete?▼

Evidence-based verification enforces a formal flow that captures fresh command outputs to substantiate success claims before declaring any release complete. This prevents unverified completion claims by requiring verifiable outputs from tests or builds.

What is the best way to prevent unverified completion claims in CI/CD pipelines?▼

Preventing unverified completion claims requires enforcing evidence-based verification before any success statement in your CI/CD pipeline. Teams must capture and analyze full command outputs to determine the truthfulness of status claims before merging or releasing.

Can I use verification checks for QA sign-off and PR closures?▼

Verification checks can be used for QA sign-off and PR closures by enforcing a formal verification flow. The process gathers verifiable command outputs and analyzes them to substantiate claims about bug fixes or tests before approving work.

Does release readiness verification require full command output analysis?▼

Release readiness verification requires full-output analysis to substantiate success claims with fresh evidence. Analyzing the complete command outputs ensures that status claims about builds or tests are truthful before any release management approval.

When do I need to run a formal verification flow in software development?▼

A formal verification flow is needed whenever a team must substantiate claims about tests, builds, or bug fixes with fresh evidence. Running this sequence before any merge or release guarantees evidence-based status updates and verified completion.

Related Skills

Explore More Software Engineering Skills→
tuantiensiutuantiensiu
1

verification-before-completion

Execute verification commands and collect test, lint, and build evidence before completion claims.

Community
Intermediate
andrewendlingerandrewendlinger
5

release

Orchestrate xmris releases from preflight checks to PyPI publication.

Community
Advanced
cedriczielcedricziel

opentelemetry-go

Instrument Go applications with OpenTelemetry for traces, metrics, and OTLP export.

Community
Advanced
idiaz01idiaz01
3

verification-before-completion

Run prescribed verification commands and report evidence-backed completion results.

Community
Advanced