qa

Automate web application QA testing with tiered test levels and health scores.

Updated May 6, 2026
One-click install
npx skills add https://github.com/stayconnectquick/gstack --skill qa-stayconnectquick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/stayconnectquick/gstack/tree/main/qa
Command: npx skills add https://github.com/stayconnectquick/gstack --skill qa-stayconnectquick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically QA test a web application to uncover defects, verify fixes, and prevent regressions across releases, saving time and reducing production incidents.

Core Features & Use Cases

  • Tiered testing: Quick, Standard, and Exhaustive tests tailored to risk and impact.
  • Health and ship-readiness: Produces before/after health scores, evidence of fixes, and a ship-readiness summary.
  • Proactive validation: Suggests tests when features are ready or when stakeholders request verification.

Quick Start

Run a QA pass on the web app and fix defects found, then re-run to verify improvements.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run QA testing on a web app to find bugs before shipping?

QA testing applies tiered systematic evaluation to a web app to identify defects. It offers Quick, Standard, and Exhaustive tiers to uncover bugs and verify fixes, generating before/after health scores and a ship-readiness summary.

What is the difference between Quick, Standard, and Exhaustive test tiers?

Quick, Standard, and Exhaustive test tiers apply different levels of systematic evaluation to a web app, tailored to risk and impact. This tiered testing approach uncovers defects and generates a ship-readiness summary based on the selected evaluation depth.

How does a ship-readiness score evaluate web application release readiness?

A ship-readiness score evaluates release readiness by summarizing before/after health scores and fix evidence. This systematic QA testing verifies that identified defects are resolved, preventing regressions across releases and confirming the web app is ready to ship.

Can I automatically verify bug fixes and prevent regressions across releases?

You can verify bug fixes and prevent regressions by running a QA pass to identify defects, applying fixes, and re-running the evaluation. This generates before/after health scores and fix evidence to verify improvements and prevent production incidents.

Does QA testing support proactive test suggestions for new web app features?

QA testing supports proactive validation by suggesting tests when features are ready or when stakeholders request verification. This proactively identifies defects in the web app and ensures fixes are verified before generating a ship-readiness summary.