skills.rest
bajajvinamr
bajajvinamrCOMMUNITY
Explore all skills by this author →
Website𝕏@axios_iiitlGitHub

gstack

Automate QA browser interactions and evidence capture via a Playwright-based daemon.

Updated Apr 1, 2026
Search Tags:#automation#screenshots#qa#playwright#headless#browse
One-click install
npx skills add https://github.com/bajajvinamr/little-wins --skill gstack-bajajvinamr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/bajajvinamr/little-wins/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/bajajvinamr/little-wins --skill gstack-bajajvinamr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, annotate screenshots, test responsive layouts, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots.

Core Features & Use Cases

  • Navigate pages, interact with UI, and inspect state across flows.
  • Diff before/after snapshots, annotate screenshots, and test responsive layouts.
  • Capture bug evidence for PRs, QA reports, and design reviews.

Quick Start

Go to a page with the browse tool and capture a snapshot to document the result.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I automate QA testing and capture screenshots of web pages?▼

Automate QA testing and capture screenshots using a Playwright-based daemon that navigates pages, interacts with UI elements, and logs outputs locally for debugging and traceability.

What is the best way to test responsive layouts across different devices?▼

Test responsive layouts across devices by running the headless browser to navigate pages, interact with elements, and capture annotated screenshots of the rendered states for review.

How do I capture bug evidence for a QA report or pull request?▼

Capture bug evidence by navigating to a page, interacting with the UI flow, and taking screenshots of the resulting state to document the issue for PRs and design reviews.

Does the QA browser support before and after snapshot diffing?▼

The QA browser supports diffing before and after snapshots, allowing you to compare page states, annotate the screenshots, and verify UI changes during deployment verification.

Can I use a headless browser to dogfood a user flow locally?▼

You can dogfood user flows locally via a persistent daemon that automates browser interactions, inspects state across flows, and captures screenshots to verify site behavior.

Why use a persistent daemon for headless browser automation?▼

A persistent daemon runs locally to automate QA tasks like navigation and screenshot capture, maintaining logged outputs that provide debugging traceability across multiple testing sessions.

Related Skills

Explore More Software Engineering Skills→
GTC6244GTC6244

gstack

Run a persistent headless browser daemon for QA testing with Bun and Playwright.

Community
Advanced
antriksh-29antriksh-29

qa-only

Generate structured QA reports with health scores, screenshots, and reproducible steps.

Community
Advanced
ohdaveedohdaveed

playwright-cli

Automate browser interactions and capture page state with Playwright CLI.

Community
Advanced
deveshkumarsdeveshkumars

gstack

Drive a headless Chromium browser to interact with webpages and capture test evidence.

Community
Advanced