skills.rest
gmliao
gmliaoCOMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Require fresh command output before asserting task, PR, or release completion.

1|Updated Nov 22, 2025
Search Tags:#verification#completion#evidence#lint#CI#tests#claim integrity
One-click install
npx skills add https://github.com/gmliao/swift-state-tree --skill verification-before-completion-gmliao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/gmliao/swift-state-tree/tree/main/.agent/skills/Superpowers/verification-before-completion
Command: npx skills add https://github.com/gmliao/swift-state-tree --skill verification-before-completion-gmliao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces honest completion by requiring fresh verification evidence before any completion claim, reducing risk of misrepresentation.

Core Features & Use Cases

  • Enforces a verification-before-claim policy across workflows (e.g., tasks, PRs, releases).
  • Provides a structured gate function workflow (IDENTIFY, RUN, READ, VERIFY, ONLY THEN) to ensure claims are substantiated.
  • Useful in CI pipelines, code reviews, and release processes to prevent premature success assertions.

Quick Start

Follow the Gate Function steps to verify work: IDENTIFY the required command, RUN it fully, READ the output, VERIFY the results, and ONLY THEN claim 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 enforce verification before claiming task completion in CI pipelines?▼

You can prevent premature success assertions in code reviews by enforcing a verification gate function that requires fresh command outputs and test results to validate task completion before approving PRs.

What is the verification-driven completion process for releases?▼

Verification-driven completion is a policy that requires fresh evidence from CI, tests, and reviews before any release success claim, reducing the risk of misrepresentation through a structured identify, run, read, and verify workflow.

How do I ensure claim integrity with fresh evidence before a PR is approved?▼

You can prevent premature success assertions in code reviews by enforcing a verification gate function that requires fresh command outputs and test results to validate task completion before approving PRs.

Does verification-before-completion work without external dependencies or components?▼

Yes, it works without external dependencies because it provides a standalone gate function workflow that operates directly on your existing CI, test, and review commands to validate task completion.

What are the limitations of using a gate function to verify task results?▼

The limitation of a gate function is that it only verifies task completion based on the specific commands you identify and run, meaning it cannot validate outcomes if the underlying verification command itself is insufficient or incorrect.

Related Skills

Explore More Software Engineering Skills→
vertexcover-iovertexcover-io
4

pipeline-setup

Provision a git worktree and run baseline metrics for pipeline setup.

Official
Intermediate
tsenseitsensei
3

land-and-deploy

Merge pull requests, trigger deployments, and verify production health via canary checks.

Community
Advanced
KSD-COKSD-CO
11

verify

Require fresh verification evidence before reporting completion claims.

Official
Advanced
RamblurrRamblurr

verification-before-completion

Run verification commands and validate output before claiming work completion.

Community
Intermediate