skills.rest
jaehun0630
jaehun0630COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Verify completion claims with fresh evidence before declaring success in code reviews and PRs.

Updated May 21, 2026
Search Tags:#verification#governance#evidence#quality-assurance#code-review#pull-request#continuous-integration
One-click install
npx skills add https://github.com/jaehun0630/cline-superpowers --skill verification-before-completion-jaehun0630
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/jaehun0630/cline-superpowers/tree/main/packages/skills/verification-before-completion
Command: npx skills add https://github.com/jaehun0630/cline-superpowers --skill verification-before-completion-jaehun0630

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work as complete or passing without verification risks delivering incomplete or faulty results. This rule promotes a trust-based, evidence-driven approach by forcing verification before any success claim.

Core Features & Use Cases

  • Verification gate: Requires running the verification command and examining fresh results before declaring completion.
  • Evidence-first policy: Encourages documenting the exact outputs that support completion status.
  • Use cases: code reviews, PR readiness checks, and release gating to ensure changes are fully validated.

Quick Start

Run the full verification command and review the output before declaring 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 verify code review completion with fresh evidence before claiming success?▼

To verify code review completion with fresh evidence, run the full verification command, examine the output, and document the exact results before declaring success to prevent premature claims.

What is an evidence-first policy for pull request readiness checks?▼

An evidence-first policy for pull request readiness requires running verification commands and recording the exact outputs that support completion status before a PR is approved or merged.

How do I enforce a verification gate during continuous integration release gating?▼

To enforce a verification gate during continuous integration release gating, mandate that verification commands are executed and fresh outputs are interpreted before any success statement is made.

Why do I need to run verification commands before declaring a task complete?▼

You need to run verification commands before declaring a task complete to prevent delivering faulty results, ensuring that all success statements are backed by fresh, examined evidence.

Can I use code review governance to prevent premature success statements in software engineering?▼

Yes, applying code review governance prevents premature success statements by requiring a verification gate that forces you to run commands and review outputs before claiming completion.

Related Skills

Explore More Software Engineering Skills→
jiroamatojiroamato

pr

Create pull requests from current branches using GitHub templates and validation checks.

Community
Intermediate
hanibalskhanibalsk
3

verification-before-completion

Run verification commands and require evidence before completion claims.

Community
Basic
billydeeii136billydeeii136

health

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

Community
Intermediate
EwallywEwallyw

verification-loop

Execute automated verification checks before claiming task completion.

Community
Advanced