skills.rest
2300031147
2300031147COMMUNITY
Explore all skills by this author →
GitHub

gstack

Run a persistent headless Chromium daemon for browser QA via CLI.

Updated Apr 12, 2026
Search Tags:#automation#qa#cli#playwright#browser#screenshot
One-click install
npx skills add https://github.com/2300031147/clawopencode --skill gstack-2300031147
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/2300031147/clawopencode/tree/main/skills
Command: npx skills add https://github.com/2300031147/clawopencode --skill gstack-2300031147

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

gstack provides a fast, persistent browser engine for QA testing and dogfooding. It lets you navigate pages, interact with elements, verify state, diff before/after, and capture bug evidence with annotated screenshots. This enables you to test deployments, reproduce issues, and document bugs quickly in a single workflow.

Core Features & Use Cases

  • Persistent headless Chromium daemon for continuous QA sessions.
  • Navigate, read, snapshot, diff, annotate, and screenshot pages; verify forms and dialogs; test responsive layouts.
  • Use cases include testing deployments, reproducing bugs, and documenting issues with visual evidence.

Quick Start

Install the skill and start by running /browse to open a site and begin QA flow.

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 for deployment verification?▼

Automate headless browser QA by running a persistent headless Chromium daemon that navigates pages, extracts text, interacts with elements, and captures annotated screenshots to verify deployments. It provides a continuous session for rapid feedback across pages.

Can I capture annotated screenshots to reproduce bugs in responsive layouts?▼

Yes, you can capture annotated screenshots to reproduce bugs in responsive layouts. The tool snapshots pages, applies diffs, and annotates elements, providing visual evidence for documenting issues across different viewport sizes.

How does a persistent headless Chromium daemon work for continuous site testing?▼

A persistent headless Chromium daemon works by maintaining a continuous browser session communicated with via a simple CLI. This allows you to navigate, snapshot, diff, and interact with pages across multiple responsive layouts without restarting the browser.

Do I need Playwright installed to run browser automation and take screenshots?▼

Playwright is listed as a core keyword for this browser automation and screenshot workflow. The tool operates via a Bash, Read, and AskUserQuestion surface to manage navigation, cookie handling, and snapshot generation.

What is the best way to diff before and after states when testing web forms?▼

The best way to diff before and after states when testing web forms is using the built-in snapshot and diff commands. You navigate to a page, interact with the form, then generate a diff with annotated screenshots to verify state changes.

How to handle cookies when automating CLI navigation for bug reproduction?▼

Handle cookies during CLI navigation for bug reproduction using the provided cookie handling surface. The tool generates a plan with frontmatter that safely manages cookie state while you interact with elements and extract text.

Related Skills

Explore More Software Engineering Skills→
lyh2lyh2

gstack

Automate QA browser sessions with a deterministic headless Chromium environment.

Community
Advanced
olaafrossiolaafrossi
10

gstack

Automate QA browser sessions with a persistent headless browser.

Community
Advanced
danieldev24danieldev24

ci-cd-and-automation

Automates CI/CD pipeline setup and quality gates for code verification.

Community
Advanced
timurgaleevtimurgaleev
5

browse

Automate QA flows with a persistent headless Chromium session.

Community
Advanced