skills.rest
LisztVan
LisztVanCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Require fresh command output and exit codes before reporting task completion.

2|Updated Apr 24, 2026
Search Tags:#testing#verification#release#evidence#code-review#build-validation
One-click install
npx skills add https://github.com/LisztVan/subcli-cpp --skill verification-before-completion-lisztvan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/LisztVan/subcli-cpp/tree/main/.pi/skills/superpowers/skills/verification-before-completion
Command: npx skills add https://github.com/LisztVan/subcli-cpp --skill verification-before-completion-lisztvan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents false completion claims by requiring fresh verification evidence before any success statement is made, reducing mistakes, rework, and trust loss.

Core Features & Use Cases

  • Fresh Evidence First: Run the exact command that proves a task is complete, then inspect its output and exit status.
  • Works Across Delivery Tasks: Use it for builds, tests, bug fixes, releases, PRs, and any workflow where correctness must be demonstrated.
  • Practical Benefit: It keeps agents and humans aligned on evidence-based reporting, so “done” means verified rather than assumed.

Quick Start

Before you say a task is complete, run the relevant verification command, read the fresh output, and only then report 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 build and test results before claiming a task is complete?▼

To verify build and test results, run the exact command that proves completion, inspect the fresh output and exit code, and only report success after confirming a zero failure count.

What is evidence-based verification for software delivery tasks?▼

Evidence-based verification requires capturing fresh command output, exit codes, and failure counts to confirm task completion, preventing premature success claims and reducing rework in delivery workflows.

Can I use this verification process for pull requests and bug fixes?▼

Yes, this verification process works across delivery tasks including builds, tests, bug fixes, releases, and pull requests, requiring fresh command evidence to prove correctness before reporting success.

How do I stop automated agents from reporting false completion on code reviews?▼

To stop false completion claims, require agents to run build validation and test commands, read the latest output, and verify a zero exit code before stating a code review or delivery task is done.

What is the best way to prove a software release is actually verified?▼

The best way to prove a release is verified is to execute the relevant build validation command, capture its fresh output and failure count, and use that evidence rather than assumption to confirm success.

Related Skills

Explore More Software Engineering Skills→
ajsai47ajsai47
11

verification-before-completion

Require fresh verification evidence before claiming code completion or fixes.

Community
Intermediate
RysnzRysnz
1

verification-before-completion

Run verification commands and report completion status with evidence.

Community
Advanced
heyallencaoheyallencao
118

ks-verify

Run automated test suites and coverage checks to validate code claims.

Community
Intermediate
pmarashianpmarashian
2

testing-fallback-strategies

Execute sequential fallback testing strategies when browser automation fails.

Community
Advanced