skills.rest
tyroneross
tyronerossCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

auto-verify

Automate visual and functional UI verification with pre- and post-edit scans.

1|Updated Dec 30, 2025
Search Tags:#automation#testing#ui#accessibility#validation#hmr
One-click install
npx skills add https://github.com/tyroneross/interface-built-right --skill auto-verify-tyroneross
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-verify
Source: https://github.com/tyroneross/interface-built-right/tree/main/skills/auto-verify
Command: npx skills add https://github.com/tyroneross/interface-built-right --skill auto-verify-tyroneross

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill eliminates the manual effort of checking UI changes after every edit by automatically capturing baselines, scanning for regressions, and reporting visual or functional discrepancies.

Core Features & Use Cases

  • Automated Baseline Capture: Silently records UI state before and after code edits to detect unintended changes.
  • Verdict Reporting: Provides clear pass/fail/review feedback directly to the AI agent, including contrast issues and missing attributes.
  • Use Case: When refactoring a complex dashboard component, this skill automatically verifies that no layout elements were broken or accessibility standards violated during the HMR cycle.

Quick Start

Enable the auto-verify workflow by creating an .ibr/config.json file in your project root with autoVerify set to true and your dev server URL configured.

Frequently Asked Questions about auto-verify

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

FAQPage Schema
How do I automate UI regression testing during local web development?▼

Automate UI verification by capturing state baselines before and after web edits to detect visual discrepancies. This requires configuring an .ibr/config.json file and running a local development server to execute hook-based scans successfully.

What is the best way to check for accessibility issues after a UI edit?▼

Checking for accessibility issues after a UI edit is handled by automated verdict reporting, which flags problems like contrast issues and missing attributes. The scanner applies this validation continuously during the development cycle to ensure standards are not violated.

Do I need a running local development server to validate UI changes?▼

Yes, a running local development server is required to validate UI changes. The automated verification process relies on hook-based scanning against the active server environment to capture baselines and report discrepancies during the HMR cycle.

How does automated baseline capture work for web component refactoring?▼

Automated baseline capture works by silently recording the UI state before and after code edits to detect unintended changes. When refactoring web components, it automatically verifies that no layout elements were broken or accessibility standards were violated.

Can I integrate visual verification into my continuous integration workflow?▼

Yes, you can integrate visual verification into continuous integration workflows by setting autoVerify to true in your .ibr/config.json file. This applies continuous design intent validation and interaction assertions directly to your web development process.

Related Skills

Explore More Software Engineering Skills→
first-flukefirst-fluke
218

backend-development

Build Python backends with FastAPI, PostgreSQL, and Redis.

Official
Intermediate
BasharAmsoBasharAmso
1

Launch Checklist

Automate pre-launch validation and generate a pass/fail readiness report.

Community
Intermediate
tyronerosstyroneross
1

design-implementation

Compares live rendered UI state against defined design intent for web, iOS, and macOS.

Community
Advanced
chmonitorchmonitor
255

ui-ux-audit

Audit ClickHouse Monitor dashboard routes for UI regressions and accessibility violations.

Official
Advanced