skills.rest
amanik
amanikCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gstack

Automate headless browser QA workflows with persistent sessions and visual diffs.

Updated Mar 31, 2026
Search Tags:#automation#qa#Playwright#browser#headless#gstack
One-click install
npx skills add https://github.com/amanik/sailor-score-debug --skill gstack-amanik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/amanik/sailor-score-debug/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/amanik/sailor-score-debug --skill gstack-amanik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly verify UI flows and bug reproduction by running a persistent, fast headless browser against your app. It enables QA testers to load pages, interact with elements, validate states, diff results, annotate screenshots, and test responsive layouts without manual browser fiddling.

Core Features & Use Cases

  • Persistent browser daemon: Keep cookies, sessions, and state across commands for realistic QA sessions.
  • Comprehensive command surface: Navigate, read, interact, inspect, and visualize pages with screenshots and diffs.
  • Evidence-driven QA: Capture diffs, annotate screenshots, and validate layouts across breakpoints to reproduce and report bugs.

Quick Start

Launch the CLI and load a URL, then capture an annotated screenshot to report a bug.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I automate headless browser QA testing for bug reproduction?▼

Automate headless browser QA testing by loading pages, interacting with elements, and validating states to reproduce bugs. A persistent browser daemon maintains sessions while you capture annotated screenshots and visual diffs for reporting.

Can I maintain persistent sessions and cookies across browser automation commands?▼

Yes, you can maintain persistent sessions and cookies across browser automation commands. The persistent browse daemon keeps your state intact, enabling realistic QA testing workflows without losing your session between interactions.

How do I capture annotated screenshots and visual diffs during Playwright testing?▼

Capture annotated screenshots and visual diffs during Playwright testing by navigating pages and invoking the visualization commands. This evidence-driven QA approach validates layouts and documents exact UI states for bug reports.

Does this headless browser tool support responsive layout checks across breakpoints?▼

Yes, this headless browser tool supports responsive layout checks across breakpoints. You can validate your application's UI at different viewport sizes to ensure layouts render correctly and reproduce responsive design bugs.

What is the best way to verify UI flows without manual browser fiddling?▼

The best way to verify UI flows without manual browser fiddling is running a fast headless browser against your app. It automates navigation, state verification, and interaction, capturing visual evidence to report bugs efficiently.

Why use a persistent browse daemon for QA testing instead of standard browser automation?▼

A persistent browse daemon keeps cookies and state alive across commands, providing a continuous QA session. Standard browser automation often resets state, making it harder to reproduce complex user flows and realistic testing scenarios.

Related Skills

Explore More Software Engineering Skills→
Intension-usIntension-us

gstack

Automate QA browsing with a persistent headless browser for navigation and verification.

Official
Advanced
olaafrossiolaafrossi
10

gstack

Automate QA browser sessions with a persistent headless browser.

Community
Advanced
reomgitreomgit

browse

Interact with web pages and capture screenshots using a headless browser.

Community
Advanced
bravohenrybravohenry

dev-browser

Automate browser interactions with persistent page state for complex workflows.

Community
Intermediate