skills.rest
elophanto
elophantoCOMMUNITY
Explore all skills by this author →
Website𝕏@elophantoGitHub

verification-before-completion

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

116|9|Updated Feb 18, 2026
Search Tags:#verification#quality#evidence#verify#ci#pull-request
One-click install
npx skills add https://github.com/elophanto/EloPhanto --skill verification-before-completion-elophanto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/elophanto/EloPhanto/tree/main/skills/verification-before-completion
Command: npx skills add https://github.com/elophanto/EloPhanto --skill verification-before-completion-elophanto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification leads to unreliable results and hidden regressions. This skill enforces evidence-based completion by requiring fresh verification outputs before any success claims.

Core Features & Use Cases

  • Enforce a verification gate before PRs, merges, releases, or stakeholder updates.
  • Execute verification commands and evaluate outputs to confirm success or surface failures with evidence.
  • Applicable to code changes, test suites, builds, and deployment workflows, ensuring trust across the delivery pipeline.

Quick Start

Run the verification workflow on your latest changes to generate a verification report.

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 before claiming a pull request is complete?▼

To enforce verification before claiming a pull request is complete, execute your build and test commands, read the outputs, and require fresh pass/fail evidence before signaling completion or merging.

Why does claiming work is done without verification lead to hidden regressions?▼

Claiming work is done without verification leads to hidden regressions because unvalidated code changes bypass the quality gate, allowing untested builds and failing tests to silently enter the delivery pipeline.

What is the best way to verify code changes before a release or stakeholder update?▼

The best way to verify code changes before a release or stakeholder update is to execute the verification workflow on your latest changes to generate a verification report with fresh evidence.

Can I use this verification gate for both test suites and deployment workflows?▼

Yes, you can use this verification gate for both test suites and deployment workflows, as it applies to any development workflow where code, tests, or builds must be validated before signaling completion.

How do I generate a verification report with evidence for my latest changes?▼

To generate a verification report with evidence for your latest changes, run the verification workflow, which executes validation commands, evaluates outputs, and reports pass/fail status with evidence.

Related Skills

Explore More Software Engineering Skills→
mrkhachaturovmrkhachaturov

verification-before-completion

Runs a verification flow before allowing work to be marked complete.

Community
Advanced
Ab0umarAb0umar

verification-before-completion

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

Community
Advanced
smarmen86smarmen86

ship

Automate branch merging, test execution, adversarial review, versioning, and pull request creation.

Community
Advanced
roanbrasilroanbrasil
5

static-analysis

Automate static analysis for Java, Kotlin, Python, and Rust codebases.

Community
Advanced