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 verification by mapping changed files to routes and driving a real browser against your local dev server. ## Core Features & Use Cases - Scoped Test Discovery: Accepts a PR number, branch name, or 'current' and uses git diff or GitHub CLI to determine which files changed, then maps them to testable routes. - Automated Browser Interaction: Uses the agent-browser CLI to open pages, snapshot interactive elements, click, fill forms, and capture screenshots in headed or headless mode. - Pipeline and Manual Modes: In pipeline mode it finds a free port and auto-starts the dev server; in manual mode it asks the user for preferences and pauses for human verification of OAuth, email, payment, or SMS flows. - Use Case: After opening a PR that modifies user settings views, run the Skill to automatically load /settings, verify key elements render, click through critical interactions, screenshot the results, and receive a pass/fail summary table. ## Quick Start Ask the agent to run browser tests on the current branch changes, for example by invoking /ce-test-browser with no arguments.
