qa

Run systematic QA tests on web applications with a headless browser.

127k|19.1k|Updated Mar 11, 2026

Search Tags:#automation #testing #qa #regression testing #bug detection #web application

Ready to run

npx skills add https://github.com/garrytan/gstack --skill qa-garrytan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/garrytan/gstack/tree/main/qa
Command: npx skills add https://github.com/garrytan/gstack --skill qa-garrytan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of thoroughly testing web applications, identifying bugs, and ensuring a high-quality user experience.

Core Features & Use Cases

Automated Testing: Performs systematic exploration of web applications, mimicking user interactions.
Mode Flexibility: Supports diff-aware testing on feature branches, full application scans, quick smoke tests, and regression analysis against baselines.
Use Case: After deploying a new feature, run /qa to automatically test affected pages, verify functionality, and catch regressions before they reach production.

Quick Start

Run a quick smoke test on the current application.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I automate regression testing for web applications after deploying new features?▼

Automated regression testing for web applications systematically explores affected pages using a headless browser to verify functionality and catch bugs before they reach production. It mimics user interactions to identify visual, functional, and performance issues.

What is diff-aware testing and when do I need it for feature branches?▼

Diff-aware testing is a mode that systematically targets only the affected pages of a web application based on feature branch changes. You need it to efficiently catch regressions and document UX issues without running a full application scan.

Can I run a quick smoke test on a web application to check basic functionality?▼

You can run a quick smoke test on a web application to rapidly verify basic functionality and identify critical visual or accessibility issues. This testing mode provides a structured report with health scores and evidence without deep exploration.

Does headless browser testing detect accessibility and performance issues?▼

Headless browser testing detects accessibility and performance issues by systematically exploring web applications and mimicking user interactions. It documents these problems alongside functional and UX bugs into a structured report with health scores.

What's the best way to document visual bugs and UX issues during web application testing?▼

The best way to document visual bugs and UX issues is through systematic web application testing that generates structured reports with evidence. This approach identifies problems across various testing modes and provides health scores for tracking quality.