browse

Drive a headless browser to automate QA actions and record interaction logs via Playwright in Bun/Node runtimes.

Updated Mar 19, 2026

Search Tags:#automation #testing #qa #playwright #headless #browse

Ready to run

npx skills add https://github.com/shaneholloman/ship --skill browse-shaneholloman

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, diff.

What problem does it solve?

This Skill enables automated, repeatable browser testing by driving a headless browser to navigate URLs, interact with UI elements, and capture evidence for bugs and deployments.

Core Features & Use Cases

Headless browser automation for QA: navigate pages, interact with elements, verify state, and capture screenshots or diffs.
Regression and bug reproduction: reproduce user flows and compare before/after results with built-in snapshot support.
End-to-end testing workflow: integrate with feature development to validate deployments and QA checks across browsers and viewport sizes.

Quick Start

Launch or invoke the skill in your feature workflow and start testing a URL to verify a user flow and collect evidence.

Frequently Asked Questions about browse

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

FAQPage Schema

How do I automate headless browser testing for QA validation?▼

Headless browser testing for QA validation is automated by driving a headless browser to navigate URLs, interact with UI elements, and capture evidence like screenshots or diffs. This enables repeatable end-to-end checks for feature validation and deployments.

Can I use Playwright to reproduce bugs and compare UI snapshots?▼

Yes, Playwright can reproduce bugs by driving headless browser interactions and comparing before-and-after results with built-in snapshot support. This allows you to verify user flows and capture evidence for regression testing across different viewport sizes.

What's the best way to verify end-to-end user flows across responsive layouts?▼

The best way to verify end-to-end user flows across responsive layouts is by driving a headless browser to navigate pages, interact with forms and dialogs, and capture UI state. This validates deployments and feature behavior across multiple viewport sizes.

Do I need Node or Bun to run automated browser tests with Playwright?▼

Yes, you need a Bun or Node runtime to execute automated browser tests with Playwright. The testing commands and context management are implemented within these environments to drive the headless browser and record interaction logs.

Does headless browser automation support navigation across forms and dialogs?▼

Headless browser automation supports navigation across forms, dialogs, and responsive layouts by driving UI element interactions. It applies to feature validation, deployment verification, and bug reproduction while recording interactions in logs.

Why capture screenshots and diffs during deployment verification?▼

Capturing screenshots and diffs during deployment verification provides visual evidence of UI state before and after changes. This enables automated regression testing by comparing built-in snapshots to detect unexpected layout or visual shifts.