browse

Drive a persistent headless Chromium browser to automate QA testing and site dogfooding.

Updated Apr 16, 2026

Search Tags:#automation #web-testing #headless #browse #dogfooding #qa-testing #visual-diffs

Ready to run

npx skills add https://github.com/vib795/copilot-anatomy --skill browse-vib795

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/vib795/copilot-anatomy/tree/main/.github/skills/gstack-browse
Command: npx skills add https://github.com/vib795/copilot-anatomy --skill browse-vib795

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent headless Chromium enables automated QA testing and site dogfooding by providing a repeatable browser context that remembers state across invocations.

Core Features & Use Cases

Navigate any URL and interact with page elements
Verify page state, capture annotated screenshots, and compute diffs between runs
Check responsive layouts and test forms, dialogs, and file uploads
Reproduce bugs and validate fixes in a deterministic, scriptable way

Quick Start

Run the one-time setup, then use the browse commands to load URLs, interact with page elements, and capture results.

Frequently Asked Questions about browse

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

FAQPage Schema

How do I automate QA testing with a persistent headless browser?▼

You can automate QA testing by driving a persistent headless browser that remembers state across invocations, enabling repeatable feature verification, regression checks, and bug reproduction in a deterministic, scriptable flow.

Can I capture screenshots and compute visual diffs during web testing?▼

Yes, you can capture annotated screenshots and compute visual diffs between test runs. This visual validation helps detect layout regressions and verify page state changes across different pages automatically.

How do I test forms, dialogs, and file uploads in headless Chromium?▼

You can test forms, dialogs, and file uploads by navigating to any URL and interacting with page elements directly. The scriptable flow supports responsive layout checks and validates these interactive UI components deterministically.

Does this headless browser approach work for reproducing bugs and validating fixes?▼

Yes, the persistent browser context is designed for bug reproduction and fix validation. It provides a deterministic, scriptable environment that ensures consistent state across multiple testing and dogfooding invocations.

What do I need to set up before running headless browser automation for site dogfooding?▼

You need to run a one-time setup to configure the environment. After setup, you use browse commands to load URLs, interact with page elements, and capture testing results for site dogfooding.