capture-release-evidences-ag

Automate browser validation of new UI features and capture WebP evidence recordings.

44.0k|5.9k|Updated Feb 13, 2026

Search Tags:#qa #browser automation #regression testing #ui validation #release evidence #webp recording #changelog mapping

Ready to run

npx skills add https://github.com/diegosouzapw/OmniRoute --skill capture-release-evidences-ag

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: capture-release-evidences-ag
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/.agents/skills/capture-release-evidences-ag
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill capture-release-evidences-ag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of missing or regressing UI changes by automatically running a browser-automation workflow that validates the newest release and captures visual evidence.

Core Features & Use Cases

Release-to-UI mapping: Reviews the latest CHANGELOG to identify newly deployed UI areas (e.g., settings tabs, provider/model listings, feature modals).
Automated browser validation: Drives a browser-automation subagent to navigate to the target pages and verify that key UI elements render and behave correctly.
Evidence capture as WebP: Produces WebP recording artifacts named for each feature validation so teams can attach proof to release checks and QA notes.
Example use case: After deploying v3.x, validate that the CLI Tools settings and a newly added provider configuration modal render correctly and record an evidence WebP for each area.

Quick Start

Run the skill while OmniRoute is accessible (for example at http://192.168.0.15:20128) and let it follow the workflow to generate WebP evidence for each identified UI change.

Frequently Asked Questions about capture-release-evidences-ag

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

FAQPage Schema

How do I capture visual release evidence for UI validation after a deployment?▼

Automated browser validation reviews the latest CHANGELOG to identify newly deployed UI areas like settings tabs and configuration modals. It maps each changelog entry to specific navigation-and-check tasks, driving a browser-automation agent to verify key UI elements render correctly across dashboard tabs.

Do I need an accessible OmniRoute URL to run automated UI regression testing?▼

What is the best way to map CHANGELOG updates to specific UI navigation tasks?▼

How does WebP recording work for capturing UI regression testing proof?▼

Can I generate a written Markdown report that inlines WebP evidence recordings?▼

Why use browser automation for release evidence instead of manual UI checks?▼