skills.rest
yuma588
yuma588COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run verification commands and inspect outputs before claiming completion.

2|Updated Jan 7, 2026
Search Tags:#git#testing#verification#evidence#pr#software#claims
One-click install
npx skills add https://github.com/yuma588/skill-gallery --skill verification-before-completion-yuma588
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/yuma588/skill-gallery/tree/main/skill-gallery-deploy/skills/community/superpower/verification-before-completion
Command: npx skills add https://github.com/yuma588/skill-gallery --skill verification-before-completion-yuma588

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide enforces a verification-first approach to claiming completion, ensuring that every success claim is backed by fresh verification evidence rather than assumptions.

Core Features & Use Cases

  • Enforces a structured verification workflow: identify the command, run the full verification, read and evaluate output, and verify the claim with evidence.
  • Prevents premature success claims by requiring fresh, verifiable results before any commit, PR, or release note.
  • Use Case: before merging a feature or bug fix, run verification steps and only proceed when outputs confirm success.

Quick Start

Before claiming completion, run the full verification workflow and review the evidence output.

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 changes before claiming a PR is complete?▼

Verifying code changes before a PR requires running a structured workflow: identify the command, run full verification, read the output, and confirm results before reporting completion.

What is a verification-first approach for software releases?▼

A verification-first approach ensures every success claim in release notes is backed by fresh, verifiable evidence rather than assumptions, preventing premature completion claims before commits.

How do I stop making premature success claims on git commits?▼

To stop making premature success claims on git commits, enforce a formal verification step requiring running commands and inspecting actual outputs to confirm results before reporting success.

Does this verification workflow require any specific testing frameworks?▼

No specific testing frameworks are required. The verification workflow applies to code commits and PRs by coordinating command execution and output inspection to determine success claims.

When do I need to run formal verification steps during software engineering?▼

You need to run formal verification steps before merging a feature or bug fix, ensuring verification outputs confirm success before proceeding with any commit, PR, or release note.

What are the limitations of using output evidence for verification claims?▼

A limitation of using output evidence for verification claims is that success requires a formal step of running commands and inspecting fresh results, preventing claims without verifiable proof.

Related Skills

Explore More Software Engineering Skills→
mortenbroesbymortenbroesby
1

verification-before-completion

Enforce fresh verification evidence before any completion claim.

Community
Intermediate
obraobra
269.6k

verification-before-completion

Verify completion claims by running commands and checking output.

Community
Basic
jagreehaljagreehal
3

verification-before-completion

Run verification commands and report outputs before completion claims.

Community
Intermediate
visualityplvisualitypl
4

debug

Analyze logs, SQLite database state, and git history to diagnose software issues.

Official
Intermediate