skills.rest
JBonfim
JBonfimCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

cy-final-verify

Require fresh verification runs with cited command output before completion claims.

Updated May 15, 2026
Search Tags:#verification#pull requests#quality gates#ci-cd#git commits#evidence reporting#test pipelines
One-click install
npx skills add https://github.com/JBonfim/skill-developer --skill cy-final-verify-jbonfim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cy-final-verify
Source: https://github.com/JBonfim/skill-developer/tree/main/.agents/skills/cy-final-verify
Command: npx skills add https://github.com/JBonfim/skill-developer --skill cy-final-verify-jbonfim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents agents from claiming completion, success, or readiness to commit/PR without running fresh, scope-matched verification evidence.

Core Features & Use Cases

  • Evidence-gated completion: Requires running the correct verification command after code changes and before any success or satisfaction language.
  • Scope-matching verification: Ensures narrow checks (e.g., unit tests) cannot justify broad claims (e.g., “task complete” or “ready to commit”); mandates the full pipeline when the claim is broad.
  • Pre-commit and pre-PR safety: Forces a full verify gate, diff sanity checks, and evidence-based reporting before creating durable repository artifacts.
  • Verification report with command output: Demands a structured report that cites the exact executed command, exit code, and output-derived verdict.

Quick Start

Use cy-final-verify whenever you are about to report success, hand off work, or create a commit/PR, and include the verification command output plus a PASS/FAIL verdict for the specific claim being made.

Frequently Asked Questions about cy-final-verify

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

FAQPage Schema
How do I prevent false success claims in CI/CD pipelines before a pull request?▼

To enforce verification before pull requests, run the full test pipeline and diff sanity checks to generate a structured report citing the exact command, exit code, and PASS/FAIL verdict before creating durable repository artifacts.

What is scope-matching verification for git commits?▼

Scope-matching verification ensures narrow checks like unit tests cannot justify broad claims like task complete or ready to commit. It mandates executing the full verification pipeline whenever a broad claim is made, preventing overstatement of readiness.

How do I generate an evidence report with test pipeline output?▼

Generate an evidence report by executing the required verification command, confirming the exit code and output failures, then reporting a structured verification report that cites the exact executed command and its output-derived verdict.

Does evidence-gated completion work for agent handoffs?▼

Evidence-gated completion applies to agent handoffs by requiring fresh, scope-matched verification runs before completion or satisfaction language is used. It ensures correctness is demonstrated through actual test pipeline execution during change lifecycle moments.

Related Skills

Explore More Software Engineering Skills→
daviddatuX25daviddatuX25

verification-before-completion

Enforce fresh verification evidence before claiming task completion.

Community
Advanced
Ab0umarAb0umar

verification-before-completion

Verify completion claims across commits, PRs, builds, and deployments with fresh evidence.

Community
Advanced
fredrikaverpilfredrikaverpil
253

git-commit

Validate git commit messages against the Conventional Commits specification.

Community
Basic
jr2804jr2804

verification-before-completion

Execute verification commands and analyze outputs before asserting completion.

Community
Basic