skills.rest
keji94
keji94COMMUNITY
Explore all skills by this author →
GitHub

gstack

Launch headless browser sessions to navigate and test web pages.

Updated Apr 4, 2026
Search Tags:#screenshot#headless-browser#qa-testing#site-dogfooding#responsive-check
One-click install
npx skills add https://github.com/keji94/content-scanner --skill gstack-keji94
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/keji94/content-scanner/tree/main/.claude/skills/.claude/skills/gstack
Command: npx skills add https://github.com/keji94/content-scanner --skill gstack-keji94

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Testing and validating web applications manually is slow and error‑prone, especially when ensuring responsive layouts, form interactions, and visual regressions across deployments.

Core Features & Use Cases

  • Headless navigation: Open pages, click elements, and evaluate state without a UI.
  • Responsive layout checks: Verify how sites render on different screen sizes.
  • Annotated screenshots: Capture before/after visuals with highlights for bug evidence.
  • Use case example: A developer can run gstack to automatically log into a staging site, perform a workflow, and receive a screenshot package for QA review.

Quick Start

Ask gstack to open a website, perform the required actions, and return an annotated screenshot of the final page.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I capture annotated screenshots for QA testing using a headless browser?▼

You can capture annotated screenshots for QA testing by launching a headless browser session to navigate pages, interact with elements, and generate visual outputs with highlights for bug evidence.

What's the best way to verify responsive layouts across deployments without a UI?▼

Verifying responsive layouts without a UI involves using a headless browser to open web pages and check how sites render across different screen sizes during development and deployment workflows.

How does headless navigation work for automated site dogfooding workflows?▼

Headless navigation for site dogfooding works by opening pages, clicking elements, and evaluating application state without a graphical interface to validate functionality and user workflows.

Do I need to install any specific tools locally to run headless browser tests?▼

Yes, you need the gstack tool installed locally to run headless browser tests, which may invoke Bash commands such as gstack, browse, design, bun, and npx during execution.

Can I automate logging into a staging site and return screenshots for QA review?▼

Yes, you can automate logging into a staging site by running a headless browser to perform the required workflow and receive a screenshot package for QA review.

Related Skills

Explore More Software Engineering Skills→
dogeareddogeared

setup-browser-cookies

Import Chromium cookies into a headless session via picker UI for authenticated QA flows.

Community
Intermediate
antriksh-29antriksh-29

qa-only

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

Community
Advanced
Jia-Hong-PengJia-Hong-Peng

gstack

Automate persistent headless browser QA testing with Playwright and Chromium.

Community
Advanced
bughqbughq
2

stacks-browse

Run headless browser QA and SPA navigation checks via Chrome DevTools Protocol.

Official
Advanced