browse

Automate end-to-end QA workflows with a persistent headless browser.

Updated Nov 11, 2025

Search Tags:#automation #testing #qa #playwright #ui-testing #headless #chromium

Ready to run

npx skills add https://github.com/rshelekhov/dotfiles --skill browse-rshelekhov

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a persistent, headless browser to automate QA workflows, enabling navigation, interaction, state capture, and evidence generation for bug reproduction and deployments.

Core Features & Use Cases

Persistent browser state: maintains cookies, sessions, and context across commands for end-to-end testing.
Comprehensive UI interactions: supports goto, text, click, fill, screenshot, diff, and accessibility snapshot to validate UI behavior.
Real-world QA scenarios: ideal for validating deployments, bug reproduction, regression testing, and testing responsive layouts across features like forms and dialogs.

Quick Start

Launch the skill, navigate to a URL with goto, and capture an accessibility snapshot to verify the page structure.

Frequently Asked Questions about browse

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

FAQPage Schema

How do I automate end-to-end QA testing with a headless browser?▼

Automating end-to-end QA testing with a headless browser involves provisioning a persistent Chromium runtime that can navigate pages, interact with elements, and capture states to validate deployments and reproduce bugs.

Can I maintain browser sessions and cookies across multiple Playwright commands?▼

Yes, maintaining browser sessions and cookies across multiple Playwright commands is supported through a persistent browser state, preserving context for end-to-end testing workflows.

Does headless UI testing support capturing screenshots and accessibility snapshots?▼

Headless UI testing supports capturing screenshots and accessibility snapshots to validate UI behavior, providing clear error reporting to aid debugging across forms and dialogs.

Do I need a Playwright-capable Chromium runtime for automated regression testing?▼

Yes, a Playwright-capable Chromium runtime is required for automated regression testing to ensure deterministic task execution and comprehensive UI interactions like goto, click, and fill.

What is the best way to validate responsive layouts during deployments without a GUI?▼

Validating responsive layouts during deployments without a GUI is best achieved using a headless browser to navigate pages and capture states for testing across user flows.

Why does headless browser automation fail to interact with certain UI elements?▼

Headless browser automation may fail to interact with certain UI elements due to dynamic page loading, requiring clear error reporting and accessibility snapshots to aid debugging.