skills.rest
ilderaj
ilderajCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run verification commands and require fresh evidence before completion claims.

Updated Apr 11, 2026
Search Tags:#verification#governance#evidence#quality-assurance#code-review#software-engineering
One-click install
npx skills add https://github.com/ilderaj/superpowering-with-files --skill verification-before-completion-ilderaj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/ilderaj/superpowering-with-files/tree/main/harness/upstream/superpowers/skills/verification-before-completion
Command: npx skills add https://github.com/ilderaj/superpowering-with-files --skill verification-before-completion-ilderaj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before making any completion claim, teams need proof and fresh verification to avoid premature or dishonest assertions in software tasks.

Core Features & Use Cases

  • Enforces a formal verification gate before commits, PRs, or releases.
  • Guides users through identifying the proving command, executing it, inspecting results, and recording evidence.
  • Applicable to development workflows where verifiable results, accountability, and auditability are required.

Quick Start

Verify with fresh evidence before completion.

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 code review verification before a pull request is completed?▼

Code review verification requires executing the full proving command and inspecting the complete output to support completion claims. This process enforces a formal verification gate before commits or PRs, ensuring accountability and auditability.

What is fresh evidence verification in software engineering governance?▼

Fresh evidence verification is a governance mechanism requiring proof before commits, PRs, or releases. It prevents premature completion claims by enforcing a formal verification gate to ensure accountability and auditability in software engineering workflows.

How do I prevent premature or dishonest completion claims in development workflows?▼

Preventing premature completion claims requires identifying the proving command, executing it, and recording fresh evidence. This enforces a formal verification gate before commits or PRs, ensuring accountability and auditability in development workflows.

Does this verification approach work with existing quality assurance workflows?▼

This verification approach works with existing quality assurance workflows by enforcing a formal verification gate before commits, PRs, or releases. It guides users through identifying proving commands, executing them, and recording evidence for auditability.

What are the limitations of enforcing a verification gate before task completion?▼

The limitation of enforcing a verification gate is that it requires identifying and running the full proving command, then reading complete output to support claims. If verification fails, the process halts, preventing task completion until results are supported.

Related Skills

Explore More Software Engineering Skills→
lagz0nelagz0ne
2

verification-before-completion

Enforce fresh verification evidence before claiming work completion.

Community
Basic
alo-expalo-exp
6

GSD — Security Review

Review code changes against OWASP defense-in-depth and generate SECURITY.md gates.

Official
Advanced
csharpfritzcsharpfritz
18

Testing Expert

Generate unit tests and analyze code coverage for software projects.

Community
Intermediate
nth5693nth5693
370

code-review

Automate multi-perspective code reviews with structured checklists and workflow prompts.

Community
Basic