ce-test-browser

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

Updated May 11, 2026
One-click install
npx skills add https://github.com/mmnavarr/harness --skill ce-test-browser-mmnavarr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-test-browser
Source: https://github.com/mmnavarr/harness/tree/main/skills/ce-test-browser
Command: npx skills add https://github.com/mmnavarr/harness --skill ce-test-browser-mmnavarr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-browser.

What problem does it solve? Manually verifying that every page touched by a pull request still renders and behaves correctly is slow and error-prone. This Skill automates browser-based smoke testing of exactly the routes affected by your current changes, catching rendering errors, console failures, and broken interactions before merge. ## Core Features & Use Cases - Scoped Test Discovery: Maps changed files from a PR number, branch diff, or current branch to concrete application routes (Rails views/controllers, Next.js pages, components, stylesheets). - Automated Browser Interaction: Uses the agent-browser CLI to open pages, snapshot interactive elements, click, fill forms, and capture viewport or full-page screenshots. - Environment Management: Detects a free dev-server port, auto-starts the server in pipeline mode, and supports headed or headless execution. - Failure Handling & Reporting: Documents failures with screenshots, supports human verification for OAuth/email/payment flows, and produces a structured pass/fail summary table. - Use Case: After opening a PR that modifies user settings views, run the Skill with the PR number to automatically load each affected route, verify key elements render, and receive a results table with any console errors. ## Quick Start Ask the AI to run browser tests on the current branch changes, for example by saying "run browser tests for PR 847" or "test the pages affected by my current branch".

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 browser tests on pages changed in a PR?▼

Pass the PR number as the argument, and the Skill fetches changed files via gh pr view, maps them to routes, and tests each page with agent-browser. You can also pass a branch name or 'current' to diff against main.

How do I test a specific branch or custom dev server port?▼

Pass the branch name to diff it against main, or append --port followed by a port number to override automatic port detection. Without arguments, the Skill tests the current branch's changes.

What is agent-browser and why is it required?▼

agent-browser is the CLI used exclusively for all browser automation in this workflow, including navigation, element snapshots, clicks, form fills, and screenshots. The Skill stops and instructs you to run the setup command if agent-browser is not installed.

Can browser tests run automatically in a CI or pipeline environment?▼

Yes, pipeline mode skips interactive questions, defaults to headless execution, scans for a free port, and auto-starts the dev server if none is listening. Manual mode instead asks the user about headed mode and requires the server to be running.

What happens when a browser test fails?▼

The Skill captures a screenshot of the error state, documents reproduction steps, and asks whether to fix the issue immediately or skip and continue. All outcomes are recorded in a final summary table with console errors and an overall PASS, FAIL, or PARTIAL result.