skills.rest
pv-udpv
pv-udpvCOMMUNITY
Explore all skills by this author →
GitHub

Verification Before Completion

Run full verification commands and report evidence-backed status before completion.

4|2|Updated Jan 19, 2026
Search Tags:#verification#completion#evidence#quality-assurance#pull-request#tests
One-click install
npx skills add https://github.com/pv-udpv/pplx-unofficial-sdk --skill verification-before-completion-pv-udpv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Verification Before Completion
Source: https://github.com/pv-udpv/pplx-unofficial-sdk/tree/main/.cline/skills/community/skills/debugging/verification-before-completion
Command: npx skills add https://github.com/pv-udpv/pplx-unofficial-sdk --skill verification-before-completion-pv-udpv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claims about completion are only valid when backed by fresh verification evidence to prevent unverified success.

Core Features & Use Cases

  • Enforces a step-by-step verification protocol before signaling completion.
  • Guides running a full verification command, evaluating results, and reporting outcomes with evidence.
  • Suitable for builds, tests, PR readiness, and any task where accuracy matters.

Quick Start

Run the full verification sequence and report the results 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 before claiming a build or test is complete?▼

To enforce verification before completion, implement a step-by-step protocol requiring a full command run, inspecting fresh output, and reporting evidence-backed status. This prevents unverified success claims by validating tasks with actual results.

What is evidence-backed pull request readiness and why is it needed?▼

Evidence-backed pull request readiness requires fresh command output from builds or tests to validate task accuracy. It is needed to prevent unverified success, ensuring completion claims are strictly supported by actual verification results before proceeding.

How do I prevent unverified success when running quality assurance checks?▼

Prevent unverified success during quality assurance by running a full verification command, evaluating the fresh output, and reporting outcomes with evidence. This protocol ensures no completion signal is sent without validated task results.

Can I use a step-by-step verification protocol for any workflow validation?▼

Yes, you can apply a step-by-step verification protocol to any workflow where tasks must be validated with fresh command output. It guides running full verification sequences and reporting evidence-backed status for builds, tests, or pull requests.

Related Skills

Explore More Software Engineering Skills→
J-PsterJ-Pster
291

verification-before-completion

Enforces fresh verification evidence before allowing completion claims in builds, tests, lints, or migrations.

Community
Advanced
HohlasHohlas
3

verification-before-completion

Run verification commands and report fresh outputs before completion claims.

Community
Intermediate
billydeeii136billydeeii136

health

Compute a weighted 0-10 codebase health score and track trends over time.

Community
Intermediate
yongwoonyongwoon
8

ywc-verify-done

Enforce a five-step verification gate for completion claims using fresh shell command output.

Community
Advanced