gstack

Automate end-to-end QA workflows with a headless browser via Playwright.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Analog-Labs/pixelport-launchpad --skill gstack-analog-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/Analog-Labs/pixelport-launchpad/tree/main/.agents/skills/gstack
Command: npx skills add https://github.com/Analog-Labs/pixelport-launchpad --skill gstack-analog-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, diff.

What problem does it solve?

gstack enables automated QA workflows by driving a headless browser to navigate pages, interact with UI elements, and verify state, removing manual testing bottlenecks.

Core Features & Use Cases

  • Persistent browser automation for reliable replays of user flows.
  • Diff, annotate, and screenshot capabilities to document test results.
  • Multi-viewport testing to validate responsive layouts and UI consistency.

Quick Start

Run bun install, then run the browse CLI to begin QA testing a page.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I automate end-to-end QA testing for user flows?

Automate end-to-end QA testing by using a headless browser to navigate pages, interact with UI elements, and verify state. This approach removes manual testing bottlenecks and enables reliable replays of user flows for feature validation.

Can I take screenshots and diff UI changes during browser automation?

Yes, you can take screenshots and diff UI changes during browser automation. The Skill provides diff, annotate, and screenshot capabilities to document test results and capture visual regressions across tested pages.

Does this QA testing tool support multi-viewport testing for responsive layouts?

Yes, this QA testing tool supports multi-viewport testing to validate responsive layouts. It drives a headless browser across different viewport sizes to ensure UI consistency and layout correctness for public sites and internal apps.

Do I need Playwright installed to run headless browser QA workflows?

Yes, you need Playwright installed to run headless browser QA workflows. The Skill relies on Playwright for browser automation and Bun for its runtime, requiring you to run bun install before starting the browse CLI for testing.

How does headless browser automation handle cookies and sessions for regression testing?

Headless browser automation handles cookies and sessions by using a local state store to persist them. This allows reliable replays of user flows during regression testing without needing to re-authenticate for every test run.