skills.rest
All-The-Vibes
All-The-VibesOFFICIAL
Explore all skills by this author →
GitHub

test-browser

Automate end-to-end browser tests for PR-driven changes using agent-browser CLI.

50|14|Updated Mar 11, 2026
Search Tags:#automation#testing#e2e#browser#agent-browser#pr-testing
One-click install
npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill test-browser-all-the-vibes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/All-The-Vibes/ATV-StarterKit/tree/main/.github/skills/test-browser
Command: npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill test-browser-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Run end-to-end browser tests on pages affected by PRs or branch changes using the agent-browser CLI to catch UI regressions before merge.

Core Features & Use Cases

  • End-to-end browser testing of PR- and branch-driven changes using agent-browser.
  • Automatically determine test scope from changed files, map them to routes, and verify the local dev server is running.
  • Capture interactive snapshots, perform basic interactions, and generate screenshots to validate UI consistency across headed and headless modes.
  • Suitable for CI workflows and manual QA to ensure critical pages render correctly after changes.

Quick Start

Run the test-browser skill on your PR or branch to start automated browser tests against changed pages.

Frequently Asked Questions about test-browser

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

FAQPage Schema
How do I run end-to-end browser tests only on pages changed by a PR?▼

To run end-to-end browser tests on PR-changed pages, the skill automatically derives test scopes from git diffs, maps changed files to corresponding routes, and validates them using the agent-browser CLI against your running dev server.

Do I need a running development server to test UI changes in a branch?▼

Yes, testing UI changes in a branch requires a reachable development server. The automated browser testing process depends on the local server to load routes, render pages, and execute interactive UI validations against the changes.

Can I use headless browser testing for UI regressions in CI workflows?▼

Yes, headless browser testing for UI regressions in CI workflows is fully supported. The skill operates in both headed and headless modes to capture interactive snapshots, generate screenshots, and validate UI consistency without a display.

What is the best way to catch UI regressions before merging a pull request?▼

The best way to catch UI regressions before merging is automated branch-driven browser testing. By mapping git diff changes to application routes, the tests validate forms, interactions, and rendering on affected pages before merge.

Does automated PR testing require agent-browser to be installed separately?▼

Yes, automated PR testing requires agent-browser to be installed separately. The skill relies on the agent-browser CLI as its core dependency to execute tests, interact with pages, and capture screenshots across local routes.

Related Skills

Explore More Software Engineering Skills→
xotongxotong

ce-test-browser

Automate end-to-end browser tests for pages affected by PRs or branches.

Community
Advanced
eysenfalkeysenfalk

agent-browser

Automate browser interactions for web testing, form filling, screenshots, and data extraction.

Community
Advanced
plurigridplurigrid
60

qa-regression

Automate Playwright-based QA regression tests for login, dashboard, and user management flows.

Official
Advanced
cin12211cin12211
218

playwright-expert

Automate cross-browser end-to-end tests with Playwright and Node.js.

Community
Intermediate