browser-test

Generate and validate YAML browser-test prompts from code changes.

1|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/ReefBytes-Owner/Manifest --skill browser-test-reefbytes-owner
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-test
Source: https://github.com/ReefBytes-Owner/Manifest/tree/main/configs/claude/skills/browser-test
Command: npx skills add https://github.com/ReefBytes-Owner/Manifest --skill browser-test-reefbytes-owner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create, update, and manage browser-use YAML test prompts for end-to-end browser testing. Analyzes code changes to generate targeted test definitions. Auto-triggers when new frontend pages, API resolvers, or user-facing features are added.

Core Features & Use Cases

  • Auto-generate YAML browser-test prompts from code changes
  • Manage tests in tests/browser/ and templates
  • Validate YAML schemas and support create/list/dry-run workflows
  • Integrates with the browser-use CLI for execution and reporting

Quick Start

Run the browser-test skill to generate or validate YAML browser tests from your latest code changes.

Frequently Asked Questions about browser-test

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

FAQPage Schema
How do I automate e2e browser testing from code changes?▼

Automate e2e browser testing by detecting frontend code changes and auto-generating YAML test prompts under tests/browser/ to validate new routes, API resolvers, and UI features via the browser-use CLI.

How do I create and validate YAML schemas for browser tests?▼

Create and validate YAML schemas for browser tests using supported create, list, and dry-run actions. The workflow validates schemas against defined conventions before executing e2e tests with the browser-use CLI.

Does browser-use work with YAML-based e2e testing workflows?▼

Yes, browser-use integrates with YAML-based e2e testing workflows by executing generated YAML test prompts. It validates new frontend pages and API resolvers, then handles execution and reporting.

Can I auto-generate test definitions when new UI features are added?▼

Yes, auto-generate test definitions when new UI features, frontend pages, or API resolvers are added. The workflow analyzes code changes and triggers targeted YAML browser-test prompt generation automatically.

What is the best way to manage e2e test prompts for new frontend routes?▼

Manage e2e test prompts for new frontend routes by storing templates and tests under tests/browser. Apply create, list, and dry-run actions to validate YAML schemas and maintain test definitions across projects.

When should I use YAML browser tests instead of manual e2e validation?▼

Use YAML browser tests instead of manual validation when applying changes across multiple projects that introduce new routes, components, or integrations, so you can trigger auto-prompt generation and standardize schema validation.