test-browser

Name: test-browser
Availability: InStock
Author: apollostreetcompany

Automate end-to-end browser tests on pages affected by pull request changes.

Updated Mar 23, 2026

Search Tags:#CI/CD #automated testing #browser testing #end-to-end testing #front-end development

Ready to run

npx skills add https://github.com/apollostreetcompany/codex-compound --skill test-browser-apollostreetcompany

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/apollostreetcompany/codex-compound/tree/main/plugins/compound-engineering/skills/test-browser
Command: npx skills add https://github.com/apollostreetcompany/codex-compound --skill test-browser-apollostreetcompany

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates browser testing on web pages affected by changes in a pull request or branch, ensuring that functionality remains intact and saving time on manual testing.

Core Features & Use Cases

Automated Browser Testing: Execute end-to-end browser tests automatically.
Customizable Scope: Test a specific PR, branch, or current changes.
Integration with Development Environments: Seamlessly integrates with local development servers and various CLI tools.
Use Case: If you're working on a feature branch and want to ensure that your changes haven't broken the application, this Skill can automatically run tests for you.

Quick Start

Run browser tests for the current branch with the command: /test-browser

Frequently Asked Questions about test-browser

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

FAQPage Schema

How do I automate end-to-end browser testing for a specific pull request?▼

You can automate end-to-end browser testing for a specific pull request by running the `/test-browser` command, which targets web pages affected by your branch changes to ensure functionality remains intact.

What do I need to run automated browser tests on affected web pages?▼

To run automated browser tests on affected web pages, you need the `agent-browser` CLI for browser automation and a running local development server to execute your front-end application.

Can I customize the scope of end-to-end testing to only check current branch changes?▼

Yes, you can customize the scope of end-to-end testing to only check current branch changes, allowing you to focus specifically on the web pages affected by your recent code modifications.

How does automated browser testing fit into a continuous integration workflow?▼

Automated browser testing fits into a continuous integration workflow by automatically executing end-to-end tests on affected web pages during regression testing, saving time on manual verification for front-end applications.

Does this browser testing approach work with local development servers?▼

Yes, this browser testing approach works directly with local development servers, using the `agent-browser` CLI to automate regression testing against your running front-end application environment.