ce-test-browser

Automate browser testing of web pages changed in pull requests or branches using agent-browser CLI.

14|3|Updated May 7, 2026
One-click install
npx skills add https://github.com/Ouro-labs/ouroboros-plugins --skill ce-test-browser-ouro-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-test-browser
Source: https://github.com/Ouro-labs/ouroboros-plugins/tree/main/plugins/compound-engineering/assets/skills/ce-test-browser
Command: npx skills add https://github.com/Ouro-labs/ouroboros-plugins --skill ce-test-browser-ouro-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-browser, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill automates browser testing for web pages affected by pull requests or branch changes, saving time and reducing manual effort.

Core Features & Use Cases

  • Automated Browser Testing: Run end-to-end tests on web pages affected by code changes.
  • Integration with Development Tools: Uses agent-browser CLI for browser automation.
  • Use Case: When a pull request is created or a branch is updated, this Skill can automatically test the affected pages to ensure functionality and UI integrity.

Quick Start

Run tests for the current branch using: /ce-test-browser

Frequently Asked Questions about ce-test-browser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate browser testing for pull requests and branch changes?

Automated browser testing for pull requests runs end-to-end tests on web pages affected by code changes, using the agent-browser CLI for browser automation to verify functionality and UI integrity without manual effort.

What do I need to run automated browser testing locally?

Automated browser testing requires a running local development server and the agent-browser CLI installed locally to execute browser automation commands against your development environment.

How does browser testing identify which web pages to test after a branch update?

Browser testing targets web pages affected by code changes in your pull request or branch, ensuring that only the modified pages are verified for functionality and UI integrity.

Does automated browser testing work with my local development server?

Automated browser testing integrates directly with your local development server, using the agent-browser CLI to navigate and test web pages served locally to validate branch changes.

Can I run browser tests on the current branch without complex configuration?

Browser testing on the current branch can be initiated by running a single command to execute end-to-end tests against the affected web pages without complex setup.