release-verification

Name: release-verification
Availability: InStock
Author: tubtrb

Verify release readiness with focused tests, browser smoke checks, and artifact capture.

Updated Mar 15, 2026

Search Tags:#automation #documentation #verification #release #ci-cd #qa-testing #browser-evidence

Ready to run

npx skills add https://github.com/tubtrb/autoreport --skill release-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-verification
Source: https://github.com/tubtrb/autoreport/tree/main/codex/skills/release-verification
Command: npx skills add https://github.com/tubtrb/autoreport --skill release-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides release-time verification for the autoreport repository, coordinating focused tests, browser smoke checks, cross-browser validation, and collection of proof artifacts to support release notes or user guides.

Core Features & Use Cases

Focused tests, browser smoke checks, and cross-browser web-demo validation to verify that a release behaves as expected.
Artifact capture (screenshots, logs, and download evidence) to support release notes and user guides.
Deterministic, reproducible verification workflows that can feed into release signoff and documentation.

Quick Start

Run the release verification workflow to reproduce the main user flow and capture browser evidence for the current branch.

Frequently Asked Questions about release-verification

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

FAQPage Schema

How do I verify release readiness with browser evidence before deployment?▼

Release readiness verification with browser evidence executes focused tests, cross-browser smoke checks, and artifact collection to ensure release candidates behave as expected. It enforces preloads and captures screenshots or logs for documentation-ready outputs.

What is the best way to capture browser smoke checks and artifacts for release notes?▼

Capturing browser smoke checks and artifacts for release notes involves running a structured verification workflow that reproduces main user flows across major browser engines. This workflow captures screenshots, logs, and download evidence to support user guides.

Does release verification support cross-browser validation for public documentation prep?▼

Release verification supports cross-browser web-demo validation for public documentation prep by applying comprehensive checks across major browser engines. It enforces browser-evidence requirements and collects deterministic artifacts for release signoff.

How do I run deterministic, reproducible verification workflows for release signoff?▼

Deterministic, reproducible verification workflows for release signoff are executed by running focused tests and safety checks on the current branch. This structured workflow enforces preloads and generates documentation-ready outputs through artifact capture.

What limitations apply to browser evidence collection during release verification?▼

Browser evidence collection during release verification is limited to focused tests, browser smoke checks, and artifact capture for the specified repository. It applies specifically to release candidates and public documentation prep rather than general continuous integration testing.