skills.rest
Scripsteam
ScripsteamOFFICIAL
Explore all skills by this author →
GitHub

verification-before-completion

Run full verification commands and report success only with output evidence.

Updated Aug 27, 2026
Search Tags:#verification#completion#governance#evidence#pr#code-review#claims
One-click install
npx skills add https://github.com/Scripsteam/scrips-stack --skill verification-before-completion-scripsteam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Scripsteam/scrips-stack/tree/main/methodology/verification-before-completion
Command: npx skills add https://github.com/Scripsteam/scrips-stack --skill verification-before-completion-scripsteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work as complete without verification invites defects and miscommunication. This Skill enforces that completion claims are backed by fresh verification evidence before proceeding with commits, PRs, or handoffs.

Core Features & Use Cases

  • Enforce verification before status updates: run verification commands, review outputs, and only then declare success.
  • PR readiness and handoff guardrail: ensures evidence-backed claims are used during code completion, PR creation, and task transitions.
  • Auditable evidence and reporting: guides users to package verification results for future audits or reviews.

Quick Start

Run the full verification process and attach its output as evidence before making any completion claim.

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 completion claims before creating a PR?▼

Verifying task completion before a PR requires running full verification commands, evaluating their outputs, and explicitly stating success with fresh evidence. This guards against unverified claims during code reviews and task handoffs.

What does it mean to enforce verification before status updates?▼

Enforcing verification before status updates requires running full validation commands and attaching their output as evidence before reporting success. This prevents unverified completion claims and ensures results are auditable.

How do I package verification evidence for a code review handoff?▼

To package verification evidence for a code review handoff, run the full verification process and attach its output directly to your completion claims. This provides auditable proof that validates task results before reporting success.

Why should I require fresh evidence for task completion claims?▼

Requiring fresh evidence for task completion claims prevents defects and miscommunication during commits and PR handoffs. It ensures success is only stated after evaluating the output of a newly run verification command, avoiding unverified status updates.

Can I use governance checks for PR readiness without running code verification?▼

No, PR readiness governance checks require running a full verification command and evaluating its output before declaring success. You cannot bypass the verification process when making completion claims during PR creation or task transitions.

Related Skills

Explore More Software Engineering Skills→
brixtonphambrixtonpham

Verification Before Completion

Run verification commands and report outputs, exit codes, and failures before completion.

Community
Advanced
krzemienskikrzemienski
2

verification-before-completion

Require fresh verification evidence before declaring task completion.

Community
Advanced
kimprobablykimprobably

verification-before-completion

Enforces verified Git commit and PR readiness through explicit pass/fail evidence.

Community
Basic
gaebalaigaebalai
8

kiro-verify-completion

Validate task completion claims using evidence from the current code state.

Community
Intermediate