test-browser

Automate end-to-end browser tests for pages affected by Git branch changes.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ybbms777/compound-engineering --skill test-browser-ybbms777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-browser
Source: https://github.com/ybbms777/compound-engineering/tree/main/skills/test-browser
Command: npx skills add https://github.com/ybbms777/compound-engineering --skill test-browser-ybbms777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually testing every page affected by a PR or branch change is time-consuming and prone to missing regressions. This Skill automates the process of identifying affected pages and running browser tests on them, so you can catch UI issues fast without wasting effort on unaffected parts of your application.

Core Features & Use Cases

  • Automated Test Scoping: Automatically maps changed files from a PR or branch to their corresponding testable routes, so you only test relevant pages.
  • End-to-End Browser Validation: Uses the agent-browser CLI to run full browser interactions (navigation, clicks, form fills, screenshots) to verify pages render correctly and key elements work as expected.
  • Use Case: When you open a PR that updates user profile pages and settings forms, this Skill automatically detects the affected routes, runs browser tests on them, captures screenshots of any errors, and provides a clear summary of results to streamline your code review process.

Quick Start

Use the test-browser skill to run end-to-end browser tests on all pages affected by your current branch changes and get a clear pass/fail summary of results.

Frequently Asked Questions about test-browser

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

FAQPage Schema
How do I run end-to-end browser tests only for pages affected by a pull request?

End-to-end browser testing for affected pages is automated by mapping changed files in a pull request or Git branch to their corresponding routes, ensuring only modified pages are tested.

What is automated test scoping for UI validation in a Git workflow?

Automated test scoping for UI validation detects changed files in a Git branch and maps them to testable routes, eliminating manual testing of unaffected pages to catch regressions faster.

Do I need a local development server to run browser tests on a branch?

Yes, running targeted browser tests requires a local development server, Git repository access to detect changed files, and the agent-browser CLI to automate browser interactions and capture screenshots.

How does agent-browser CLI validate UI rendering after code modifications?

The agent-browser CLI validates UI rendering by executing full browser interactions including navigation, clicks, form fills, and screenshots to verify pages render correctly and key elements function as expected.

Can I automate regression testing for form functionality in specific PR changes?

Yes, you can automate regression testing for forms by detecting changed files in a PR, mapping them to affected routes, and running browser tests that fill forms and capture errors in a pass/fail summary.

What are the limitations of automated browser testing for unchanged application pages?

The testing scope is limited to routes mapped from changed Git files, meaning intentionally unaffected pages are not tested, requiring separate manual or automated testing for full application coverage.