skills.rest
xbpk3t
xbpk3tCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-browser

Run end-to-end browser tests on changed pages in a pull request or branch.

Updated Aug 23, 2026
Search Tags:#e2e#browser-testing#visual-regression#agent-browser#pr-testing#devserver
One-click install
npx skills add https://github.com/xbpk3t/ce-codex --skill test-browser-xbpk3t
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/xbpk3t/ce-codex/tree/main/skills/test-browser
Command: npx skills add https://github.com/xbpk3t/ce-codex --skill test-browser-xbpk3t

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers and reviewers need a repeatable way to validate that UI changes in a pull request or branch do not break rendering, interactions, or critical flows; this Skill automates those checks so visual regressions and broken interactions are discovered before merging.

Core Features & Use Cases

  • Map changed files to likely routes and components so only relevant pages are tested.
  • Drive a local development server with the agent-browser CLI to capture interactive snapshots, perform clicks/fills, and take screenshots in headed or headless modes.
  • Use Case: Run tests for a feature branch to verify a new dashboard component, capture failing screenshots, and create todos for follow-up fixes.

Quick Start

Run the test-browser skill to test pages affected by the current branch or a specific PR and get a summarized report of results.

Frequently Asked Questions about test-browser

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

FAQPage Schema
How do I run E2E browser tests for only the pages changed in a pull request?▼

E2E browser tests for changed pages run by mapping changed Git files to specific application routes, exercising key UI interactions, and capturing screenshots to validate rendering and functional regressions before merging.

What do I need to run visual regression tests on a local development branch?▼

Visual regression testing on a local branch requires a running local development server on a discoverable port, the agent-browser CLI to drive interactions, and Git or GitHub metadata access to identify changed files.

How does mapping changed files to routes work for PR browser testing?▼

PR browser testing maps changed files to likely routes and components so only relevant pages are tested, driving the local dev server with agent-browser to capture interactive snapshots and screenshots for functional verification.

Can I use this to verify a new dashboard component during a feature branch review?▼

Yes, you can verify a new dashboard component during a feature branch review by running the test-browser skill to capture failing screenshots, validate UI interactions, and generate summarized test reports for follow-up fixes.

Does the agent-browser CLI support headless mode for automated PR testing?▼

Yes, the agent-browser CLI supports both headed and headless modes to capture interactive snapshots, perform clicks and fills, and take screenshots for automated visual and functional verification during PR reviews.

What is the best way to automate UI rendering checks for changed pages before merging?▼

Automated UI rendering checks for changed pages use the test-browser skill to exercise key interactions via agent-browser, capture snapshots for visual verification, and create todos for any failing regressions discovered before merging.

Related Skills

Explore More Software Engineering Skills→
ybbms777ybbms777
1

test-browser

Automate end-to-end browser tests for pages affected by Git branch changes.

Community
Advanced
OpenSourceSamOpenSourceSam

finishing-a-development-branch

Finalize a development branch by closing epics, verifying tests, and presenting integration options.

Community
Advanced
xotongxotong

ce-test-browser

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

Community
Advanced
hidonguyenhidonguyen

ck:test

Execute unit, integration, e2e, and UI tests across JavaScript/TypeScript, Python, Go, Rust, and Flutter projects.

Community
Advanced