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".