skills.rest
diegosouzapw
diegosouzapwCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

capture-release-evidences-cx

Automate browser validation of released UI features and capture WebP evidence.

44.0k|5.9k|Updated Feb 13, 2026
Search Tags:#browser automation#release validation#visual evidence#UI regression testing#WebP recording#CHANGELOG-driven QA
One-click install
npx skills add https://github.com/diegosouzapw/OmniRoute --skill capture-release-evidences-cx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: capture-release-evidences-cx
Source: https://github.com/diegosouzapw/OmniRoute/tree/main/.agents/skills/capture-release-evidences-cx
Command: npx skills add https://github.com/diegosouzapw/OmniRoute --skill capture-release-evidences-cx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the uncertainty of whether newly shipped UI changes actually render correctly by automating end-to-end browser validation and producing visual evidence recordings for every release.

Core Features & Use Cases

  • Release-to-UI mapping: Reviews the latest CHANGELOG.md to identify which new or modified UI features to validate.
  • Automated browser verification: Drives a browser-automation subagent to navigate the running app, exercise target UI paths, and verify components render as expected.
  • Evidence capture for audits: Saves WebP recording evidence named per feature via a required RecordingName so reviewers can quickly confirm what changed.

Quick Start

Ask it to validate the latest release UI by running the workflow against your target OmniRoute dashboard URL (defaulting to http://192.168.0.15:20128) and capturing WebP evidence for each newly introduced UI feature.

Frequently Asked Questions about capture-release-evidences-cx

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

FAQPage Schema
How do I automate UI regression testing and capture visual evidence after a release?▼

Automate UI regression testing by reading your CHANGELOG.md for feature targets, driving browser automation to verify component rendering, and saving WebP recording evidence per feature for release QA review.

Can I use CHANGELOG-driven QA to validate newly released UI features?▼

Yes, CHANGELOG-driven QA maps newly released or modified UI features from CHANGELOG.md to automated browser verification tasks, confirming correct rendering and generating visual evidence for each update.

How does visual evidence recording work for browser automation?▼

Visual evidence recording works by running a browser-automation subagent that navigates target web app paths, verifies updated UI components, and saves a WebP recording named per feature via a required RecordingName artifact.

What do I need to set up before running automated release validation on my web app?▼

You need a running web app URL, an accessible CHANGELOG.md listing target UI features, and browser automation capabilities to execute navigation, verify component rendering, and generate WebP evidence artifacts.

Is there a way to automatically verify if shipped UI changes render correctly without manual checks?▼

Automated browser verification eliminates manual checks by driving a subagent to navigate running web app dashboards, exercise target UI paths, and confirm components render correctly while capturing WebP evidence for audits.

What are the limitations of using browser automation for UI regression testing?▼

Browser automation for UI regression testing requires a running web app instance and a structured CHANGELOG.md to identify targets, meaning offline repositories or non-web interfaces cannot be validated or recorded as WebP evidence.

Related Skills

Explore More Product & Management Skills→
diegosouzapwdiegosouzapw
44.0k

capture-release-evidences-cc

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

Community
Intermediate
MoonLadderStudiosMoonLadderStudios
12

fix-comments

Resolve GitHub pull request review comments and push validated fixes.

Official
Advanced
potatsukkipotatsukki

playwright-browser-testing

Verify UI changes in a browser with Playwright MCP after each code change.

Community
Intermediate
winstonkoh87winstonkoh87
558

visual-verify-ui

Capture multi-viewport screenshots and compare DOM states for visual regression testing.

Community
Intermediate