skills.rest
Mateo1099
Mateo1099COMMUNITY
Explore all skills by this author →
GitHub

verification-before-completion

Run full verification commands and validate output before claiming completion.

Updated Mar 29, 2026
Search Tags:#verification#code-quality#evidence-based#pre-merge#release-process#regression-check
One-click install
npx skills add https://github.com/Mateo1099/CampusFlow --skill verification-before-completion-mateo1099
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verification-before-completion
Source: https://github.com/Mateo1099/CampusFlow/tree/main/.trae/skills/verification-before-completion
Command: npx skills add https://github.com/Mateo1099/CampusFlow --skill verification-before-completion-mateo1099

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures you never claim work is complete without fresh, verifiable evidence, preventing dishonest or premature success claims.

Core Features & Use Cases

  • Enforces a step-by-step verification workflow before status changes or PR creation.
  • Guides users to identify the proving command, run it fully, read outputs, verify results, and only then claim success.
  • Use cases include before closing tasks, before PRs, or before marking a feature as done in a project.

Quick Start

Run the full verification command, inspect the output, and only claim completion if the results prove 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 verify code quality before claiming a task is complete?▼

Pre-merge verification requires identifying the proving command, running it fully, reading the output, and validating results before reporting completion status. This evidence-based process prevents premature success claims during code reviews.

What is the best way to prevent premature completion claims in a release process?▼

Preventing premature completion claims requires obtaining fresh evidence by running the full verification command and validating its output. This step-by-step release process ensures work is never marked done without verifiable proof.

How do I enforce an evidence-based regression check before a PR approval?▼

Enforce an evidence-based regression check by running the full verification command and inspecting its output before approving a PR. Only report success if the fresh output validates the results without errors.

Can I use this pre-merge verification workflow for closing software development tasks?▼

Yes, you can use this pre-merge verification workflow for closing software development tasks, creating PRs, or marking features as done. It enforces a step-by-step process to validate results before any status changes.

Why should I run a full verification command instead of partial checks before marking a feature done?▼

Running a full verification command instead of partial checks ensures you obtain fresh, verifiable evidence. This prevents dishonest or premature success claims by requiring complete output validation before reporting the final status.

Related Skills

Explore More Software Engineering Skills→
JoaquinCampoJoaquinCampo
3

verification-before-completion

Run a documented verification command and report evidence-backed completion.

Community
Basic
RysnzRysnz
1

verification-before-completion

Run verification commands and report completion status with evidence.

Community
Advanced
musical-basicsmusical-basics

github-pr-workflow

Automate GitHub pull request workflows from branch creation to merge with CI monitoring.

Community
Advanced
Miss-PinkElfMiss-PinkElf

superpowers-verification-before-completion

Enforce fresh verification evidence before SPARK-workflow completion claims.

Community
Intermediate