capture-release-evidences-cc

Run browser-driven UI validation and capture WebP recordings of OmniRoute features.

44.0k|5.9k|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/diegosouzapw/OmniRoute --skill capture-release-evidences-cc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture-release-evidences-cc
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/.agents/skills/capture-release-evidences-cc
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill capture-release-evidences-cc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the uncertainty of whether new UI features actually render correctly by automatically driving a browser-automation flow and capturing visual evidence for the latest release.

Core Features & Use Cases

  • Release-based UI validation: Reviews CHANGELOG entries to identify the specific new UI areas to verify for the current deployment.
  • Automated browser walkthroughs: Navigates to the application (local or remote URL), runs deterministic validation tasks, and verifies UI components render as expected.
  • Evidence capture as WebP recordings: Saves feature-focused WebP recording artifacts using a required RecordingName so results can be included in a final report.

Quick Start

Ask the Skill to validate the newest UI changes by running the browser automation against your OmniRoute URL (defaulting to http://192.168.0.15:20128) and generating a final Markdown artifact that inlines the WebP evidence.

Frequently Asked Questions about capture-release-evidences-cc

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

FAQPage Schema
How do I automate visual regression testing for new UI features after a deployment?

Visual regression testing validates newly released UI features by running browser-driven navigation workflows. It automatically identifies new feature areas from the CHANGELOG, verifies component rendering against expected outcomes, and captures visual evidence as WebP recordings for release reporting.

How does browser automation capture release evidence for UI validation?

Browser automation captures release evidence by navigating to the target application URL and executing deterministic validation tasks. It verifies UI components render correctly and saves visual proof as feature-focused WebP recording artifacts named by RecordingName for final report inclusion.

Can I generate WebP recordings for local UI changelog testing?

Yes, changelog testing supports local UI validation workflows. You can direct the browser automation subagent to a locally accessible URL, execute end-to-end UI regression checks, and generate WebP recordings as visual proof of local deployments.

What is the best way to verify OmniRoute UI changes after a new release?

The best way to verify OmniRoute UI changes is using automated browser walkthroughs that navigate to the application URL and run deterministic validation tasks. This approach checks specific feature areas identified from the latest CHANGELOG and outputs WebP evidence.

Do I need a remote server to run browser-driven UI validation workflows?

No, a remote server is not required. UI validation workflows can execute against any accessible target URL, defaulting to a local network address. This allows you to run browser-driven visual regression checks and capture WebP recordings locally or remotely.