skills.rest
steltz
steltzCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run verification commands and collect fresh evidence for completion claims.

Updated Mar 30, 2026
Search Tags:#validation#verification#completion#evidence#code-quality#pr-review
One-click install
npx skills add https://github.com/steltz/skill-factory --skill verification-before-completion-steltz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/steltz/skill-factory/tree/main/references/superpowers/skills/verification-before-completion
Command: npx skills add https://github.com/steltz/skill-factory --skill verification-before-completion-steltz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces risk of unverified completion claims by requiring fresh verification evidence before any success assertions.

Core Features & Use Cases

  • Enforces running verification commands to prove completion status.
  • Requires capturing fresh outputs and evidence for verifiable reporting.
  • Applies to code changes, builds, tests, and PRs across software projects.
  • Guides teams to report actual results with evidence rather than unverified promises.

Quick Start

Run the verification command for the current work item and report the output 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 a code commit is marked complete?▼

To enforce verification before completion, you run verification commands on code changes and capture the fresh output as evidence. This ensures success assertions are backed by actual results rather than unverified promises.

What is the best way to collect evidence for PR review?▼

The best way to collect evidence for PR review is to execute the full verification suite and report the status alongside the fresh outputs. This provides verifiable results that prove the completion claims for the software project.

How do I validate build and test results before claiming a task is done?▼

You validate build and test results by running the specific verification commands and requiring the resulting fresh outputs as proof. This enforces verifiable reporting by comparing actual execution evidence against completion claims.

Does this verification process work for any software project?▼

Yes, this verification process applies to code changes, builds, tests, and PRs across software projects requiring verifiable results. It enforces executing the full verification and reporting status with evidence regardless of the specific tech stack.

Why do I need fresh evidence for completion claims?▼

You need fresh evidence for completion claims to reduce the risk of unverified success assertions. Capturing fresh outputs from verification commands guides teams to report actual results with evidence rather than relying on unverified promises.

Related Skills

Explore More Software Engineering Skills→
oteroweboteroweb

verification-before-completion

Run a five-step verification workflow and report evidence before completion claims.

Community
Advanced
jchildreejchildree
1

verification-before-completion

Verify completion claims by executing and confirming command outputs before commits.

Community
Intermediate
Tommy-ywTommy-yw
539

requesting-code-review

Automate code review with static security scans and quality checks.

Community
Advanced
HohlasHohlas
3

verification-before-completion

Run verification commands and report fresh outputs before completion claims.

Community
Intermediate