skills.rest
abrahamgreyson
abrahamgreysonCOMMUNITY
Explore all skills by this author →
GitHub

gstack

Automate browser QA and visual verification in a persistent Chromium session.

Updated Aug 23, 2026
Search Tags:#automation#screenshots#qa#browser#bug verification#responsive testing#chromium
One-click install
npx skills add https://github.com/abrahamgreyson/skills --skill gstack-abrahamgreyson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/abrahamgreyson/skills/tree/main/gstack
Command: npx skills add https://github.com/abrahamgreyson/skills --skill gstack-abrahamgreyson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

gstack removes the friction of testing real web apps in a browser by giving an AI a persistent Chromium session, fast commands, and safe repeatable workflows.

Core Features & Use Cases

  • Real browser control: Navigate pages, click elements, fill forms, upload files, inspect accessibility trees, and verify that UI changes actually work.
  • Evidence-rich QA: Capture screenshots, responsive layouts, console logs, network activity, dialogs, PDFs, and before/after diffs for bug reports.
  • Production-friendly automation: Use headless mode for speed, headed mode for live watching, cookie import for authenticated flows, and ref-based selection for stable interactions.

Quick Start

Ask the gstack skill to open the target site, inspect the page, and verify the flow you want to test.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I automate browser QA with real clicks and form interactions?▼

Automated browser QA uses a persistent Chromium session to execute real clicks, fill forms, and navigate pages via ref-based element selection. This captures console logs and network activity to verify UI changes and authenticated flows work correctly.

Can I capture screenshots and console logs for bug reproduction in Chromium?▼

Capturing screenshots and console logs for bug reproduction requires running automated flows in a headed or headless Chromium session. This records network activity and UI state, generating evidence-rich visual diffs for bug reports on live web pages.

What is ref-based element selection for browser automation?▼

Ref-based element selection targets page elements using stable references rather than brittle CSS selectors. This ensures repeatable safety checks and reliable test automation when navigating pages, clicking buttons, or inspecting accessibility trees.

Does responsive testing in a persistent browser session support authenticated flows?▼

Responsive testing in a persistent browser session supports authenticated flows via cookie import. This enables production-friendly automation across different layout sizes while maintaining logged-in states for site dogfooding and visual verification.

What is the best way to verify UI changes with visual diffs in headless mode?▼

Verifying UI changes with visual diffs requires executing automated navigation in headless mode to capture before and after screenshots. This generates evidence-rich QA outputs by comparing layout states, capturing network activity, and inspecting accessibility trees.

Related Skills

Explore More Software Engineering Skills→
huichenhuichen

setup-browser-cookies

Import decrypted Chromium cookies into a Playwright headless session.

Community
Advanced
MadAppGangMadAppGang
278

browser-debugger

Automate browser UI testing and debugging with Chrome DevTools MCP.

Official
Advanced
FirzusFirzus
1

agent-browser

Automate live browser interactions and capture screenshots via CDP.

Community
Advanced
CleanExpoCleanExpo
1

playwright-browser

Automate headless browser tasks and end-to-end tests with Playwright.

Community
Advanced