cy-final-verify

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents and developers often claim work is complete, tests pass, or code is ready to commit without actually running verification commands, leading to broken builds, false handoffs, and lost trust. This Skill eliminates unverified success claims by requiring fresh command output as evidence before any completion statement. ## Core Features & Use Cases - Verification Gate: Blocks any completion, fix, or passing claim until the relevant command has been run fresh in the current session and its output inspected. - Scope Matching: Requires broad claims like "task complete" or "ready to commit" to be backed by the full verification pipeline (format, lint, tests, build), not partial checks. - Pre-Commit and Pre-PR Gate: Mandates a full pipeline run, diff review, and a structured Verification Report with a PASS verdict before any git commit or pull request. - Failure Protocol: Provides a disciplined loop for diagnosing failures, fixing root causes, and re-verifying from scratch without workarounds. - Use Case: Before an agent reports "all tests pass" and commits a bug fix, it runs the full test suite, cites the exit code and output in a Verification Report, and only then proceeds with the commit. ## Quick Start Before claiming this task is done, run the full verification pipeline and show me the verification report with the actual command output.

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

Run the full verification pipeline (formatting, linting, all tests, and build) fresh in the current session, then check the exit code and output for zero failures. Only claim completion after the output confirms it, and cite the actual command output in a verification report.

What should I check before creating a git commit or pull request?▼

Run the complete verification pipeline and confirm zero errors, warnings, and test failures. For pull requests, also review the git diff to confirm it matches the intended changes and that no unrelated files are staged.

Is running tests alone enough to claim a task is complete?▼

No. Passing tests only support the narrow claim that tests pass. A broad claim like "task complete" requires the full pipeline plus a line-by-line check of deliverables against the original requirements, since a green build does not prove requirements were met.

What should I do when verification fails?▼

Read the exact error output, diagnose the root cause without guessing, apply a minimal fix, then re-run the full verification command from scratch. Never claim partial success, skip re-verification, or move on while checks are still failing.

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 when you are about to claim success, express satisfaction with implementation state, commit, or hand off work.