gstack

Name: gstack
Availability: InStock
Author: kunalrawat425

Automate QA testing with persistent headless browser sessions and annotated screenshots.

Updated Apr 4, 2026

Search Tags:#diff #playwright #browser #screenshot #snapshot #qa-testing

Ready to run

npx skills add https://github.com/kunalrawat425/conductor-playground --skill gstack-kunalrawat425

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/kunalrawat425/conductor-playground/tree/main/.claude/skills/gstack
Command: npx skills add https://github.com/kunalrawat425/conductor-playground --skill gstack-kunalrawat425

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Persistent, fast-headless browser sessions enable repeatable QA testing, site dogfooding, and bug evidence collection without manual browser setup.

Core Features & Use Cases

Persistent, headless browser sessions with cookie and tab persistence across commands.
Snapshot, diff, and annotate modes to verify UI changes and capture evidence.
Annotated screenshots, responsive testing, and forms/dialog testing to document issues.

Quick Start

Launch the browser with /browse and start testing a site by taking a snapshot, diffing changes, and saving annotated screenshots.

Frequently Asked Questions about gstack

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

FAQPage Schema

How do I automate Playwright QA testing with persistent browser state?▼

Playwright QA testing can be automated using a fast headless browser that maintains persistent cookie and tab state across commands. This enables repeatable web testing and site dogfooding without manual browser setup.

What is the best way to capture UI diff snapshots for bug evidence?▼

The best way to capture UI diff snapshots for bug evidence is using a headless browser with dedicated snapshot and diff modes. It automatically compares UI changes and saves annotated screenshots to document issues across deployments.

Can I use a headless browser to test forms and dialogs without losing cookies?▼

Yes, you can use a headless browser to test forms and dialogs without losing cookies. It provides persistent sessions that retain cookie and tab state across multiple commands, ensuring reliable and repeatable testing.

How do I take an annotated screenshot of a website for responsive testing?▼

To take an annotated screenshot for responsive testing, launch a headless browser session and use its ready-made commands. It captures annotated screenshots to document issues and verify responsive layouts across deployments.

Does headless browser QA testing work for verifying site deployments across releases?▼

Headless browser QA testing works effectively for verifying site deployments across releases. It satisfies reliability and repeatability by offering ready-made commands, diff outputs, and annotated screenshots to collect evidence across deployments.