skills.rest
UniClipboard
UniClipboardOFFICIAL
Explore all skills by this author →
GitHub

verification-before-completion

Execute verification commands and validate fresh results before completion claims.

1.5k|69|Updated Mar 13, 2025
Search Tags:#documentation#validation#verification#quality-assurance#code-review#gating
One-click install
npx skills add https://github.com/UniClipboard/UniClipboard --skill verification-before-completion-uniclipboard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/UniClipboard/UniClipboard/tree/main/.claude/skills/verification-before-completion
Command: npx skills add https://github.com/UniClipboard/UniClipboard --skill verification-before-completion-uniclipboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Claiming work is complete without verification is dishonest, not efficient. This Skill enforces an evidence-first approach to completion, ensuring transparency and accountability in every claim.

Core Features & Use Cases

  • Evidence-driven validation: requires running fresh verification commands and reviewing outputs before declaring success.
  • Gate-style workflow: clearly identifies the command to prove status, runs it fully, and verifies the results with structured reporting.
  • Use Case: before merging a PR or releasing a feature, run verification and attach the output as proof.

Quick Start

Before making any completion claim, run the full verification sequence, review the output, and report the result with evidence.

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 evidence-based verification before declaring a task complete?▼

Evidence-based verification requires executing fresh verification commands and validating their outputs before claiming completion. This gate-style workflow ensures transparency by demanding explicit command execution and structured reporting of results as proof of status.

What is the best way to validate code review outcomes with fresh command execution?▼

Validating code review outcomes involves running targeted verification commands and reviewing the fresh results. This protocol enforces an evidence-first approach, requiring you to execute the full verification sequence and report the outcome with attached output as proof.

How do I execute a gate-style workflow to verify release readiness?▼

Executing a gate-style workflow for release readiness requires identifying the specific command to prove status, running it fully, and verifying the results. You must attach the command output as proof before merging a PR or releasing a feature.

Does verification before completion require dependencies or specific environment setup?▼

Verification before completion requires no external dependencies. It functions as an independent protocol that enforces an evidence-first approach by executing available verification commands and validating their fresh results within your current environment.

When do I need to run a full verification sequence for quality assurance?▼

You need to run a full verification sequence for quality assurance before making any completion claim, merging a PR, or releasing a feature. This protocol applies whenever task outcomes must be proven with fresh command execution and structured reporting.

Related Skills

Explore More Software Engineering Skills→
makerjackiemakerjackie
1

subagent-driven-development

Dispatch fresh subagents to execute independent tasks with two-stage reviews.

Community
Advanced
himes19himes19

land-and-deploy

Coordinate merge, CI monitoring, deployment, and production verification.

Community
Intermediate
thec3ukthec3uk

Testing Test Writing

Enforce centralized testing standards when writing test artifacts.

Official
Basic
cbleckercblecker
5

creating-commit

Automate git commit workflows with validation gates and user approval.

Community
Basic