skills.rest
steffenpharai
steffenpharaiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

browse

Automates end-to-end QA workflows via a persistent headless browser.

Updated Aug 23, 2026
Search Tags:#automation#accessibility#qa#playwright#web-testing#browser#snapshot
One-click install
npx skills add https://github.com/steffenpharai/StartupFramework --skill browse-steffenpharai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/steffenpharai/StartupFramework/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/steffenpharai/StartupFramework --skill browse-steffenpharai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end QA workflows by controlling a persistent headless browser to navigate URLs, interact with page elements, and capture evidence.

Core Features & Use Cases

  • Persistent headless browser for QA testing and dogfooding user flows.
  • Scriptable commands to navigate, interact, snapshot, and diff pages.
  • Visual evidence through screenshots and diff reports to accelerate bug reports and deployments.

Quick Start

Use the CLI to launch a session and then run commands such as "browse goto http://example.com" to start testing.

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 workflows with a headless browser?▼

Automate end-to-end QA workflows by controlling a persistent headless browser to navigate URLs, interact with page elements, and capture evidence. It uses Playwright to script commands, capture snapshots, and generate diffs for feature verification.

Can I use Playwright to capture screenshots and generate diff reports for bug reproduction?▼

Yes, Playwright captures visual evidence through screenshots and generates diff reports to accelerate bug reproduction. The CLI/API surface runs commands to snapshot pages and document user flows for local or CI environments.

What is the best way to document user flows in a local or CI environment?▼

Document user flows by launching a persistent headless browser session and running scriptable commands to navigate and interact with pages. The session captures visual evidence and diffs to verify features and reproduce bugs.

Do I need Playwright to run scriptable browser commands for feature verification?▼

Yes, Playwright is required as the browser automation engine to run scriptable commands for feature verification. It drives the persistent headless browser to navigate URLs, interact with elements, and capture snapshots.

How do I start a headless browser session to navigate and test URLs?▼

Start a headless browser session by using the CLI to launch the environment, then run commands such as goto with a target URL. This initiates the QA testing process to interact with elements and capture snapshots.

Can I run web-testing snapshots and diffs in CI environments without a display?▼

Yes, web-testing snapshots and diffs run in CI environments without a display using a persistent headless browser. It automates QA workflows by capturing visual evidence and generating diffs to support deployments.

Related Skills

Explore More Software Engineering Skills→
iani-kuliiani-kuli

webapp-testing

Automate local web app testing with Playwright and server management scripts.

Community
Intermediate
cheng80cheng80
1

gstack

Automate headless browser QA interactions and capture annotated screenshots.

Community
Advanced
lenadlmlenadlm

dogfood

Navigate web applications, capture evidence, and generate structured bug reports.

Community
Advanced
cloudofgeorgecloudofgeorge

browse

Drive a headless browser to automate QA testing and capture screenshots.

Community
Intermediate