skills.rest
TarunTeja44
TarunTeja44COMMUNITY
Explore all skills by this author →
GitHub

gstack

Automates headless Chromium browser testing for QA workflows and deployment verification.

1|Updated Feb 22, 2026
Search Tags:#e2e testing#web automation#screenshot#chromium#deployment verification#headless browser#qa testing
One-click install
npx skills add https://github.com/TarunTeja44/portfolio --skill gstack-tarunteja44
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack
Source: https://github.com/TarunTeja44/portfolio/tree/main/.agents/skills/gstack
Command: npx skills add https://github.com/TarunTeja44/portfolio --skill gstack-tarunteja44

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually testing web features, verifying deployments, and gathering visual evidence for bug reports is slow and repetitive. This Skill provides a persistent headless Chromium browser that navigates URLs, interacts with elements, asserts page states, and captures annotated screenshots at roughly 100ms per command. ## Core Features & Use Cases - Interactive Page Testing: Navigate any URL, fill forms, click elements via accessibility-tree refs, upload files, and handle dialogs automatically. - State Verification & Diffing: Assert element states (visible, enabled, checked), diff snapshots before and after actions, and inspect console errors and network requests. - Visual Evidence: Capture annotated screenshots with labeled interactive elements, responsive layout screenshots at mobile/tablet/desktop viewports, and element-level crops. - Use Case: After deploying a new login flow, navigate to the page, fill credentials using snapshot refs, click submit, diff the snapshot to confirm the dashboard appeared, and save an annotated screenshot as evidence. ## Quick Start Use the gstack browse skill to open my staging site, walk through the signup flow, and screenshot the result.

Frequently Asked Questions about gstack

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

FAQPage Schema
How do I test a login flow with a headless browser?▼

Navigate to the login page with goto, run snapshot -i to list interactive elements, fill the email and password fields using their @e refs, click submit, then verify with snapshot -D or is visible on the dashboard selector.

How to take annotated screenshots of web page elements?▼

Run snapshot -i -a -o with an output path to capture a screenshot with red overlay boxes labeling every interactive element. You can also crop to a specific element by passing its CSS selector or @ref to the screenshot command.

Can I test authenticated pages in a headless browser?▼

Yes, use cookie-import-browser to import cookies from Comet, Chrome, Arc, Brave, or Edge, either through an interactive picker or directly with a --domain flag. The session persists between commands, so authenticated pages load normally afterward.

Does headless browser testing handle JavaScript dialogs?▼

Dialogs such as alert, confirm, and prompt are auto-accepted by default to prevent browser lockup. Use dialog-accept with optional text or dialog-dismiss before triggering the action, then inspect results with the dialog command.

Why do element refs stop working after navigation?▼

Snapshot refs are invalidated whenever the page navigates because the accessibility tree is rebuilt. Run snapshot again after any goto or reload to get fresh @e refs before interacting with elements.

Related Skills

Explore More Software Engineering Skills→
bobbo01bobbo01

qa-only

Tests web applications in a browser and produces structured bug reports without fixing code.

Community
Advanced
rkumar261rkumar261
1

qa-only

Identify and document web application bugs with screenshots, console logs, and navigation paths.

Community
Advanced
eygrabereygraber
1

check

Run formatting, detekt, lint, and unit tests on Android and Kotlin projects.

Community
Intermediate
partme-aipartme-ai
610

cypress

Guide Cypress end-to-end and component testing with CI/CD configuration.

Official
Intermediate