skills.rest
Jesse-L-M
Jesse-L-MCOMMUNITY
Explore all skills by this author →
GitHub

browse

Automate browser-based QA testing with scripted interactions and screenshot diffing.

Updated Mar 27, 2026
Search Tags:#automation#testing#qa#playwright#browser#dogfooding
One-click install
npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill browse-jesse-l-m
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/Jesse-L-M/scz-target-engine/tree/main/.claude/skills/gstack/browse
Command: npx skills add https://github.com/Jesse-L-M/scz-target-engine --skill browse-jesse-l-m

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates browser-based QA testing to quickly validate site behavior, catch regressions, and gather evidence for bug reports.

Core Features & Use Cases

  • Deterministic, headless browser automation for navigating pages, interacting with elements, taking screenshots, and diffing changes.
  • Evidence capture across logs, screenshots, and test artifacts to support deployment verification and bug reproduction.
  • Use cases include CI regression checks, manual QA dogfooding, and pre-release validation of critical user flows.

Quick Start

Run a standard QA run against your app using the default browser workflow to verify core paths.

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 regression checks?▼

Headless browser QA testing automates scripted site interactions to validate outcomes and catch regressions. This Skill executes deterministic workflows across pages and forms, collecting screenshots and logs as evidence for deployment verification.

Can I use browser automation for site dogfooding and feature verification?▼

Yes, browser automation supports site dogfooding by executing scripted interactions against dynamic content. It validates critical user flows during pre-release checks, capturing test artifacts and visual diffs to reproduce bugs and verify feature behavior.

How do you capture evidence for bug reports during browser testing?▼

Evidence capture during browser testing logs screenshots, visual diffs, and test artifacts. This Skill records deterministic execution outputs across navigated pages and form interactions, providing concrete reproduction steps and deployment verification data for bug reports.

Does this QA testing approach work for validating dynamic content and forms?▼

Yes, this QA testing approach validates dynamic content and forms using a deterministic execution model. The headless browser navigates pages, interacts with elements, and applies pluggable script references to execute and verify complex user flows.

What are the limitations of using a deterministic headless browser for testing?▼

Deterministic headless browser testing requires stable, predictable scripts and may not handle non-deterministic UI behaviors or visual anomalies outside its screenshot diffing scope. It relies on pluggable script references for extensibility rather than autonomous exploration.

Related Skills

Explore More Software Engineering Skills→
Analog-LabsAnalog-Labs

browse

Drive a headless browser to load URLs, interact with elements, and verify page state.

Official
Advanced
yolopunkyolopunk

qa-only

Automate browser-based QA testing and generate structured reports with evidence.

Community
Advanced
Chachamaru127Chachamaru127
3.0k

ci

Diagnose CI/CD pipeline failures and propose remediation fixes.

Community
Intermediate
petrkindlmannpetrkindlmann
64

exploratory-testing

Guide structured exploratory testing sessions with charters, heuristics, and debrief templates.

Community
Advanced