qa

Automates web app QA testing across Quick, Standard, and Exhaustive tiers with iterative bug fixing and health scores.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/MissTully/Gstack --skill qa-misstully
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/MissTully/Gstack/tree/main/qa
Command: npx skills add https://github.com/MissTully/Gstack --skill qa-misstully

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA of web applications can be tedious and error-prone when done manually; this skill systematically automates QA testing and coordinates iterative bug fixes to ship more reliable software.

Core Features & Use Cases

  • Structured QA workflows across three tiers (Quick, Standard, Exhaustive) to match risk tolerance and time constraints.
  • Generates before/after health scores, fix evidence, and a ship-readiness summary to guide release decisions.
  • Iterative bug fixing with atomic commits and re-verification to ensure traceable improvements.

Quick Start

To start a QA cycle, invoke the qa skill with the target site and select a tier (Quick, Standard, or Exhaustive) to begin testing.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate QA testing for a web application?

Automate QA testing by invoking the skill with your target site and selecting a testing tier to systematically identify bugs and verify fixes. It coordinates iterative bug fixing with atomic commits, generating before and after health scores to track improvements.

What is the best way to triage bugs before shipping a web app?

The best way to triage bugs is running a structured QA workflow that generates a ship-readiness summary and fix evidence. It applies tiered testing across Quick, Standard, and Exhaustive levels to match your time constraints and risk tolerance.

Does automated QA testing work for live-site verification?

Automated QA testing works for live-site verification by applying structured test tiers to the deployed target site. It produces health scores and fix evidence to ensure deployed features pass verification before final release.

How do I track bug fixes with atomic commits during QA?

Track bug fixes with atomic commits by using an iterative QA workflow that re-verifies each fix. Every applied fix generates an isolated commit, ensuring traceable improvements and clear before and after health score comparisons.

Can I choose different testing depths for web app QA?

You can choose between Quick, Standard, and Exhaustive testing depths to match your specific risk tolerance and time constraints. Each tier systematically automates comprehensive QA testing and produces a corresponding ship-readiness summary.

Why do I need a ship-readiness summary for my web application?

You need a ship-readiness summary to guide release decisions based on calculated health scores and fix evidence. It provides a clear assessment of your web application's reliability after iterative bug fixing and re-verification.