verify

Name: verify
Availability: InStock
Author: xiongxianfei

Evaluate artifact-code-test coherence, evidence alignment, and release readiness.

3|Updated Apr 19, 2026

Search Tags:#evidence #traceability #quality-gate #verify #ci #artifact-management #release-readiness

Ready to run

npx skills add https://github.com/xiongxianfei/rigorloop --skill verify-xiongxianfei

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/xiongxianfei/rigorloop/tree/main/.codex/skills/verify
Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill verify-xiongxianfei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verification is a governance gate for AI-assisted software delivery, ensuring artifact-code-test coherence, evidence, and release readiness.

Core Features & Use Cases

Formalizes verification scope across specs, tests, CI workflows, and lifecycle artifacts.
Tracks evidence and traceability from plan to release, enabling auditable decisions.
Use Case: When preparing a PR, run the verification gate to confirm alignment with governing artifacts and readiness criteria.

Quick Start

Run the verifier on the current branch to produce a branch-ready report.

Frequently Asked Questions about verify

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

FAQPage Schema

How do I ensure artifact-code-test coherence before a release?▼

Traceability in CI workflows is established by tracking evidence from plan to release across lifecycle artifacts. The verification process formalizes scope across specs, tests, and CI definitions, producing documented evidence and verify-report outputs that satisfy release readiness criteria.

What is release readiness verification for AI-assisted software delivery?▼

Release readiness verification is a governance gate that ensures artifact-code-test coherence, evidence alignment, and traceability. It evaluates specs, tests, CI definitions, and lifecycle artifacts to guide reviews for branches, PRs, and releases, satisfying plan references and validated readiness criteria.

How to generate a branch-ready report for a PR verification gate?▼

A verification gate for PRs confirms alignment between code, tests, and governing artifacts like specs and CI definitions. It produces a verify-report with documented evidence and traceability, ensuring the branch meets release readiness criteria before merging.

Does release verification require specific lifecycle artifacts and plan references?▼

Yes, release verification requires lifecycle artifacts and plan references to validate readiness criteria and ensure artifact-code-test coherence. The process tracks evidence alignment across these artifacts to produce auditable verify-report evidence and release metadata.

Can I apply verification workflows to CI definitions and test artifacts?▼

Yes, verification workflows can be applied across CI definitions, test artifacts, and specs to ensure coherence and evidence alignment. This formalizes the verification scope and tracks traceability from plan to release, guiding reviews for branches and PRs.