ce-test-browser
Run browser tests for pages affected by the current branch or PR.
Install
Install this Claude and Codex skill with the command below. The command stays visible even when copy support is unavailable.
git clone https://github.com/EveryInc/compound-engineering-plugin /tmp/compound-engineering-plugin && ln -s /tmp/compound-engineering-plugin/skills/ce-test-browser ~/.claude/skills/ce-test-browserFrom README
Browser Test Skill Run end-to-end browser tests on pages affected by a PR or branch using the best approved browser driver available in the active harness. Modes Manual (default): the user controls the dev server. When the fallback driver is agent-browser, ask whether to run headed or headless. Pipeline (mode:pipeline): invoked by LFG or another automated runner. The run is unattended — never block on a question. Read references/pipeline-orchestration.md from this skill's directory and follow it; it overrides the free-port scan (step 4), dev-server startup (step 5), and visibility prompts (step 6). It still uses the preferred port that step 4 computes. Browser Driver Policy Select the driver before the first browser action: Prefer a host-native integrated browser. Use a browser-control surface embedded in or directly owned by the active harness when it can navigate local URLs, inspect rendered and interactive state, click/fill/press, capture screenshots, and inspect console errors.