skills.rest
drhazemibclc
drhazemibclcCOMMUNITY
Explore all skills by this author →
GitHub

test-browser

Runs browser-based end-to-end tests on pages affected by a PR or branch using agent-browser CLI.

Updated Mar 22, 2026
Search Tags:#automation#e2e#qa#cli#browser-testing#agent-browser#pr-testing
One-click install
npx skills add https://github.com/drhazemibclc/plate --skill test-browser-drhazemibclc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/drhazemibclc/plate/tree/main/.codex/skills/test-browser
Command: npx skills add https://github.com/drhazemibclc/plate --skill test-browser-drhazemibclc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines validating changes by running real-browser end-to-end tests on pages impacted by a PR or branch, catching CSS/layout regressions and UI issues before merging.

Core Features & Use Cases

  • Targeted testing: tests pages affected by code changes in a PR or branch.
  • Real browser validation: uses the agent-browser CLI to run tests in headless or headed mode for deterministic results.
  • Risk detection: surfaces layout, script, or navigation regressions early in CI.

Quick Start

Run end-to-end browser tests on pages affected by the current PR or branch using the agent-browser CLI.

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 on pages affected by a PR?▼

To run end-to-end browser tests on PR-affected pages, use the agent-browser CLI to execute deterministic tests in headless or headed mode. It identifies routes impacted by code changes and reports layout, script, or navigation regressions early in CI workflows.

Can I validate UI changes locally before merging a branch?▼

Yes, you can validate UI changes locally before merging by running browser-based end-to-end tests against pages affected by your branch. The agent-browser CLI executes deterministic tests to catch CSS and layout regressions prior to CI integration.

Do I need the agent-browser CLI to run deterministic browser tests?▼

Yes, the agent-browser CLI is required to run deterministic browser tests for this workflow. It powers the headless or headed browser execution needed to surface layout, script, and navigation regressions on affected routes.

How does targeted browser testing detect CSS and layout regressions?▼

Targeted browser testing detects CSS and layout regressions by running real-browser end-to-end tests only against pages affected by code changes in a PR or branch. This focused execution surfaces visual and functional UI issues before merging.

What is the best way to automate e2e testing for affected routes in CI?▼

The best way to automate e2e testing for affected routes in CI is applying a skill that uses the agent-browser CLI to run deterministic browser tests. It targets pages impacted by branch changes and reports UI regressions automatically.

When should I run browser-based e2e tests in headless or headed mode?▼

Run browser-based e2e tests in headless mode for deterministic CI workflow results, or headed mode for local validation when debugging UI changes. Both modes test PR-affected routes to catch layout and navigation regressions before merging.

Related Skills

Explore More Software Engineering Skills→
thisisryanswiftthisisryanswift
2

ce-test-browser

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

Community
Advanced
razorpayrazorpay
31

pr-action-analyzer

Analyze GitHub PR CI failures and generate structured failure reports.

Official
Advanced
vitalliumvitallium
10

ce-test-browser

Automates end-to-end browser testing of PR-affected pages using agent-browser CLI.

Community
Advanced
EhsaanArkEhsaanArk

browse

Automates headless browser QA with Playwright, capturing diffs and screenshots.

Community
Advanced