cy-final-verify

Enforces fresh verification evidence before completion claims, commits, and pull requests.

Updated May 19, 2026
One-click install
npx skills add https://github.com/lucasocosta/reeve --skill cy-final-verify-lucasocosta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cy-final-verify
Source: https://github.com/lucasocosta/reeve/tree/main/skills/cy-final-verify
Command: npx skills add https://github.com/lucasocosta/reeve --skill cy-final-verify-lucasocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Agents often claim work is complete, tests pass, or code is ready to commit without actually running verification, leading to broken builds and false handoffs. This Skill forces evidence-based completion by requiring fresh command output before any success claim. ## Core Features & Use Cases - Verification Gate: Blocks completion claims, commits, and PR creation until the full verification pipeline (formatting, linting, tests, build) has been run fresh in the current session. - Scope Matching: Ensures the verification scope matches the claim scope, so a narrow test run cannot justify a broad "task complete" claim. - Structured Reporting: Requires a standardized Verification Report citing the exact command, exit code, output summary, and a PASS/FAIL verdict. - Failure Protocol: Provides a disciplined loop for diagnosing failures, fixing root causes, and re-verifying from scratch. - Use Case: Before an agent commits a bug fix, it runs the full pipeline, confirms zero failures, emits a Verification Report, and only then proceeds with the commit. ## Quick Start Before claiming the task is done or committing, run the full verification pipeline and report the exact command output with a PASS or FAIL verdict.

Frequently Asked Questions about cy-final-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code changes before committing?▼

Run the full verification pipeline (formatting, linting, all tests, and build) after your last code change, confirm zero errors and zero test failures, then produce a Verification Report with a PASS verdict before running git commit.

What counts as valid verification evidence for a completion claim?▼

Valid evidence is fresh output from a verification command run in the current session, including the exact command, exit code, and output summary. Previous runs, partial checks, or another agent's success report do not qualify.

Does passing tests mean the task is complete?▼

No. A passing pipeline proves the code compiles, lints, and passes existing tests, but not that requirements are met. For completion claims, also verify deliverables against the original specification line by line.

What should I do when verification fails?▼

Read the exact failure output, diagnose the root cause without guessing, apply a minimal fix, then re-run the full verification command from scratch. Never claim partial success or skip re-verification after a fix.

When should this verification gate not be applied?▼

Do not apply it during early planning, brainstorming, or tasks that have not reached a concrete verification step. It activates only before success claims, commits, PR creation, or handoffs implying correctness.