browse

Name: browse
Availability: InStock
Author: singhianand23045

Drive a headless or headed browser to automate QA tasks and collect visual evidence.

Updated Apr 12, 2026

Search Tags:#automation #testing #qa #playwright #browser #diffing

Ready to run

npx skills add https://github.com/singhianand23045/GarryTan --skill browse-singhianand23045

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/singhianand23045/GarryTan/tree/main/browse
Command: npx skills add https://github.com/singhianand23045/GarryTan --skill browse-singhianand23045

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gstack browse offers a persistent headless/headed browser to streamline QA testing, site dogfooding, and bug reproduction by providing a repeatable, programmable browser workflow.

Core Features & Use Cases

Persistent headless/headed Chromium for automated QA, feature validation, and bug reproduction.
Navigate to URLs, interact with elements, fill forms, upload files, and catch dialogs.
Diffable evidence: baseline and diffed changes with annotated screenshots, logs, and state diffs.
Dogfooding and validation across deployments, accessibility checks, and responsive layout verification.

Quick Start

Open a URL with gstack browse and start interacting with elements.

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 for web apps using a headless browser?▼

Automate end-to-end QA by driving a headless browser to navigate URLs, interact with elements, and fill forms. It captures visual evidence, state diffs, and logs, returning actionable artifacts for feature verification and regression checks.

Can I capture visual diffs and screenshots during browser automation testing?▼

Yes, you can capture visual diffs and screenshots during browser automation. It provides diffable evidence by generating baseline and diffed changes with annotated screenshots and state logs for modern web apps.

Does this browser automation tool support form testing and file uploads?▼

Yes, this browser automation tool supports form testing and file uploads. It drives a persistent Chromium instance to interact with elements, fill forms, upload files, and catch dialogs during site dogfooding and bug reproduction.

What is the best way to verify responsive layouts and accessibility in automated QA?▼

The best way to verify responsive layouts and accessibility in automated QA is using a programmable browser workflow. It drives a headed or headless browser to validate deployments and capture structured state diffs across web apps.

Are there limitations when running regression checks with a headless browser?▼

Limitations of running regression checks with a headless browser generally involve environment setup and rendering differences. However, this tool provides predictable agent instructions and structured prompts to ensure repeatable, programmable browser workflows across modern web apps.