skills.rest
IAmKongHai
IAmKongHaiCOMMUNITY
Explore all skills by this author →
GitHub

ce-test-browser

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

Updated May 4, 2026
Search Tags:#browser testing#end-to-end testing#QA automation#PR testing#branch testing
One-click install
npx skills add https://github.com/IAmKongHai/compound-engineering-plugin-zh --skill ce-test-browser-iamkonghai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-test-browser
Source: https://github.com/IAmKongHai/compound-engineering-plugin-zh/tree/main/3.4.2/skills/ce-test-browser
Command: npx skills add https://github.com/IAmKongHai/compound-engineering-plugin-zh --skill ce-test-browser-iamkonghai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates end-to-end browser testing on pages affected by changes in a Pull Request or branch, ensuring quality and functionality before deployment.

Core Features & Use Cases

  • Automated Browser Testing: Run comprehensive tests on pages affected by code changes.
  • Integration with Development Environments: Works seamlessly with local development servers and the agent-browser CLI.
  • Use Case: Before merging a PR, use this Skill to automatically test all affected pages, catching potential issues early.

Quick Start

Run browser tests for the current branch with: /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 end-to-end browser testing for pages affected by a PR?▼

To automate end-to-end browser testing for affected PR pages, use this Skill to identify changed pages and run tests via the `agent-browser` CLI. It requires a local development server to execute the tests before deployment.

What is automated branch testing and how does it work with a local development server?▼

Automated branch testing runs end-to-end browser tests on pages impacted by code changes. It works by using the `agent-browser` CLI to test against your local development server, ensuring functionality before merging.

Do I need a local development server to run QA automation for affected pages?▼

Yes, you need a running local development server and the `agent-browser` CLI tool. The Skill uses these dependencies to identify affected pages and execute end-to-end browser testing successfully.

Can I use this browser testing Skill in continuous integration pipelines?▼

Yes, this Skill is suitable for continuous integration pipelines and manual testing scenarios. It automates end-to-end browser testing by identifying affected pages and executing tests using the `agent-browser` CLI.

What's the best way to catch UI issues before merging a branch?▼

The best way to catch UI issues before merging is to run automated end-to-end browser testing on affected pages. This Skill uses the `agent-browser` CLI to test your local development server and identify functionality problems early.

Why does end-to-end testing require the agent-browser CLI?▼

End-to-end testing requires the `agent-browser` CLI because it is the core tool this Skill uses to automate browser interactions. It drives the testing logic against your local development server to verify affected pages.

Related Skills

Explore More Software Engineering Skills→
udecodeudecode
240

test-browser

Execute end-to-end browser tests on pull request-affected pages using agent-browser CLI.

Official
Advanced
SantiagoisperSantiagoisper

ce-dogfood-beta

Automates backend and frontend quality checks for your selected branch, comparing with master and fixing issues found during automated testing.

Community
Advanced
xotongxotong

ce-test-browser

Automate end-to-end browser tests for pages affected by PRs or branches.

Community
Advanced
BozhidarN7BozhidarN7

agent-browser

Automate web interactions including navigation, form submission, and data scraping.

Community
Advanced