test-browser

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

Updated May 11, 2026
One-click install
npx skills add https://github.com/mmnavarr/harness --skill test-browser-mmnavarr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/mmnavarr/harness/tree/main/skills/test-browser
Command: npx skills add https://github.com/mmnavarr/harness --skill 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 end-to-end browser testing of only the pages affected by your current PR or branch, catching regressions before merge. ## Core Features & Use Cases - Scoped Test Discovery: Maps changed files (views, controllers, components, stylesheets) to concrete routes so you only test what changed. - Automated Browser Interaction: Uses the agent-browser CLI to navigate pages, snapshot interactive elements, click, fill forms, and capture screenshots in headed or headless mode. - Failure Handling & Reporting: Documents failures with screenshots, offers fix/todo/skip options, and produces a structured pass/fail summary with console errors and human verification results. - Use Case: You open a PR that modifies the settings controller and a Stimulus component. Run the Skill with the PR number, and it detects the dev server port, visits /settings and related pages, exercises key interactions, and reports any console errors. ## Quick Start Ask the assistant to run browser tests on the current branch changes, optionally specifying a PR number, branch name, or port such as "test PR 847 on port 5000".

Frequently Asked Questions about 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?▼

Invoke the Skill with a PR number, branch name, or 'current'. It uses gh or git diff to list changed files, maps them to routes, then drives agent-browser to open each page, snapshot interactive elements, and verify content.

What is agent-browser and how is it installed?▼

agent-browser is a CLI for browser automation covering navigation, clicks, form fills, and screenshots. Install it globally with npm install -g agent-browser, then run agent-browser install to set up the browser runtime.

Can I run browser tests in headed mode to watch them?▼

Yes. The Skill asks whether you want headed or headless mode before testing. Choosing headed passes the --headed flag to agent-browser so a visible browser window opens during the test run.

How does the Skill detect the dev server port?▼

It checks an explicit --port argument first, then AGENTS.md or CLAUDE.md for port references, then package.json dev scripts, then .env files for PORT=, and finally falls back to port 3000.

What happens when a browser test fails?▼

The Skill screenshots the error state, records reproduction steps, and asks whether to fix the issue immediately, create a p1 todo via the todo-create skill, or skip and continue testing remaining pages.