verify

Automate browser-based UI verification with Shiplight MCP tools.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ShiplightAI/codex-plugin --skill verify-shiplightai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify
Source: https://github.com/ShiplightAI/codex-plugin/tree/main/agents/skills/verify
Command: npx skills add https://github.com/ShiplightAI/codex-plugin --skill verify-shiplightai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifying frontend changes often requires manual, time-consuming checks across layouts, states, and interactions. This skill automates browser-based visual verification using Shiplight MCP tools to provide repeatable, native-feeling validation of UI changes.

Core Features & Use Cases

  • Visual verification of UI changes in a real browser across pages and components.
  • Session-based testing with steps to start a dev session, inspect DOM, interact with elements, and capture evidence for debugging.
  • Generates concise reports and evidence suitable for PR reviews, CI checks, and regression dashboards.

Quick Start

Launch a Shiplight MCP browser session on the target page and run verify to confirm the UI renders as expected.

Frequently Asked Questions about verify

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

FAQPage Schema
How do I automate visual regression testing for UI changes in a browser?

Automate visual regression testing by running scripted browser interactions that inspect the DOM, perform actions, and capture evidence to verify UI changes. This provides repeatable validation across pages, components, and states in local development or CI pipelines.

What is browser-based UI verification and when do I need it for frontend development?

Browser-based UI verification automates native-feeling validation of frontend changes using real browser sessions. You need it when manual checks across layouts, states, and interactions become time-consuming, ensuring repeatable visual regression testing for your components.

Do I need MCP browser automation capabilities to run session-based UI checks?

Yes, you need MCP browser automation capabilities to start sessions, inspect the DOM, interact with elements, and capture evidence. These MCP tools are required to execute the scripted interactions and checks for verifying UI changes.

Can I use automated UI verification in CI pipelines and PR reviews?

Yes, you can use automated UI verification in CI pipelines and PR reviews. The session generates concise reports and debugging evidence suitable for CI checks and regression dashboards, confirming that the UI renders as expected after changes.

How do I start a dev session to visually verify UI components?

To visually verify UI components, launch a Shiplight MCP browser session on the target page and run the verification steps. The session inspects the DOM, performs scripted interactions, and captures evidence to confirm the UI renders correctly.

What's the best way to capture evidence for debugging frontend layout issues?

The best way to capture evidence for debugging frontend layout issues is using session-based browser automation. It runs scripted interactions, inspects the DOM, and captures visual evidence, generating summarized reports for regression dashboards and PR reviews.