skills.rest
thisisryanswift
thisisryanswiftCOMMUNITY
Explore all skills by this author →
𝕏@thisisrsyanswiftGitHub

ce-test-browser

Automate end-to-end browser tests on PR-affected pages using agent-browser CLI.

2|Updated Apr 30, 2026
Search Tags:#automation#testing#end-to-end#ui-testing#browser-testing#agent-browser#pr-diff
One-click install
npx skills add https://github.com/thisisryanswift/zellij-agent-tools --skill ce-test-browser
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-test-browser
Source: https://github.com/thisisryanswift/zellij-agent-tools/tree/main/.opencode/skills/ce-test-browser
Command: npx skills add https://github.com/thisisryanswift/zellij-agent-tools --skill ce-test-browser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR and branch changes often introduce UI regressions; this skill automates end-to-end browser tests on pages touched by a PR or branch, saving time and catching issues early.

Core Features & Use Cases

  • Discover changed routes from the current PR or branch and map them to testable pages.
  • Run end-to-end browser tests using the agent-browser CLI in headed or headless modes.
  • Generate quick test summaries and capture interactions for verification.

Quick Start

Run the skill on your current branch to validate affected pages with agent-browser.

Frequently Asked Questions about ce-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 affected by a PR?▼

Automated browser testing of PR-affected pages identifies changed routes from your current branch or pull request, maps them to testable pages, and runs end-to-end tests using the agent-browser CLI to validate rendering and interactions.

What is PR diff-based UI testing and how does it prevent regressions?▼

PR diff-based UI testing analyzes your pull request changes to discover affected routes, then automatically executes browser tests on those specific pages to catch visual and interaction regressions early before merging.

Do I need a running local server to automate browser testing on branch changes?▼

Yes, automated browser testing of PR-affected pages requires both the agent-browser CLI tool and a running local server to execute end-to-end tests and validate page rendering and interactions.

Can I run headless browser tests for end-to-end UI verification?▼

Yes, end-to-end browser tests support both headed and headless modes through the agent-browser CLI, allowing you to validate page rendering and capture interactions for verification in your preferred environment.

What's the best way to automate UI testing for changed routes in a pull request?▼

Automating browser tests on PR-affected pages discovers changed routes from your branch, maps them to testable pages, and runs end-to-end tests via agent-browser to generate quick test summaries and catch UI regressions.

Related Skills

Explore More Software Engineering Skills→
jikig-aijikig-ai
12

test-browser

Map changed files to routes and run browser tests with screenshots.

Official
Advanced
mvillmowmvillmow
18

extract-test-failures

Parse test logs to extract and categorize failures by type.

Community
Basic
timurgaleevtimurgaleev
5

ship

Automate test execution, version bumps, changelog updates, and PR creation.

Community
Advanced
srpadronosrpadrono
11

pathfinder

Map user journeys and generate Mermaid coverage diagrams for UI tests.

Community
Advanced