cy-final-verify

Verify code completion with tests, linters, and builds before commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a robust verification process before claims, commits, or PRs to maintain code quality and honesty.

Core Features & Use Cases

  • Pre-Commit and Pre-PR Gate: Ensures evidence is present before claims of success, completion, or readiness for a PR or commit.
  • Full Verification Pipeline: Executes and validates all steps including tests, linters, and builds.
  • Verification Report Template: Encourages comprehensive evidence submission for claims of success or completion.
  • Failure Protocol: Provides a clear process for diagnosis, fixing, and re-verification after failure.

Quick Start

Use the cy-final-verify skill before pushing a commit by executing 'cy-final-verify run 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 verify code readiness before committing or creating a PR?

To verify code readiness before a commit or PR, execute a full verification pipeline that runs tests, linters, and build tools to ensure completion claims are backed by evidence. This enforces a strict pre-commit gate against failures.

What is a pre-commit verification gate for code integrity?

A pre-commit verification gate is a protocol requiring comprehensive evidence of success before allowing a commit or PR. It enforces code integrity by validating that all tests, linters, and build tools pass without failures.

Do I need a complete set of tests and linters to use code verification protocols?

Yes, automated code verification requires a complete set of tests, linters, and build tools to function properly. These pipeline components are mandatory to validate correctness and compliance before any significant commit.

What is the best way to report code verification evidence for a pull request?

The best way to report code verification evidence is by using a structured verification report template. This enforces comprehensive evidence submission for success claims, ensuring completion is fully documented before creating a PR.

What happens when a pre-PR verification pipeline fails?

When a pre-PR verification pipeline fails, a failure protocol is triggered that provides a clear process for diagnosis, fixing, and re-verification. This ensures code issues are fully resolved before attempting another commit.