cy-final-verify

Enforce fresh verification evidence before commits or pull requests.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unverified claims of task completion, test passes, or code readiness lead to broken builds, wasted time, and misplaced trust. This Skill ensures that every success statement is backed by fresh, reproducible verification evidence before any commit, pull‑request, or handoff.

Core Features & Use Cases

  • Gate Function: Enforces a step‑by‑step verification protocol before any claim, including running the full verification pipeline and checking exit codes.
  • Verification Report Template: Generates a structured report with command, output, exit code, and verdict that must be cited as evidence.
  • Pre‑Commit / Pre‑PR Checks: Integrates the verification gate into git workflows, preventing commits or PRs without passing verification.
  • Failure Handling: Guides agents through diagnosing, fixing, and re‑verifying failures before proceeding.

Quick Start

Ask the skill to run the full verification pipeline and produce a verification report before creating a commit.

Frequently Asked Questions about cy-final-verify

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

FAQPage Schema
How do I enforce verification checks before a git commit or pull request?

To enforce verification before a commit or pull request, you need a gate function that runs full test, lint, and build pipelines, checking exit codes to block unverified claims. This ensures every success statement is backed by fresh, reproducible evidence.

What is a verification gate in CI workflows?

A verification gate in CI workflows is a protocol that requires executing a full verification command and generating a structured report with command, output, exit code, and verdict before allowing any task completion claim, commit, or pull request to proceed.

How do I generate a structured verification report for test and build compliance?

You generate a structured verification report by running the full verification pipeline and documenting the command, output, exit code, and final verdict. This report must be cited as evidence to validate requirement compliance prior to moving forward.

How do I handle verification failures when preparing a pull request?

When handling verification failures before a pull request, you must diagnose the issue, fix the failing code, and execute re-verification through the gate protocol. Proceeding is blocked until the full pipeline passes with fresh evidence.

Do I need to run lint and build checks separately for pull-request verification?

No, you do not need to run lint and build checks separately. The verification gate requires execution of a single full verification command that validates test, lint, build, and requirement compliance together before generating the final report.