qa

Run tiered end-to-end web app tests and iteratively fix defects.

Updated Apr 1, 2026

Search Tags:#testing #qa #web-application #bug-fix #health-score #ship-readiness

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA tackles the challenge of manual, error-prone web-app testing by providing a systematic, repeatable workflow that catches issues early and documents fixes.

Core Features & Use Cases

Tiered QA plans (Quick, Standard, Exhaustive) to align testing effort with risk and project needs.
Automated testing and atomic bug-fix loop: run tests, commit each fix atomically, and re-verifiy.
Observability and reporting: before/after health scores, fix evidence, and a ship-readiness summary to guide releases.

Quick Start

Ask me to run qa on your web app to start automated QA, fix bugs, and re-verify the fixes.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I run automated end-to-end QA testing on my web application?▼

Automated end-to-end QA testing for web apps runs iterative test cycles to detect defects, fixes source code atomically, and re-verifies to produce before/after health scores and a ship-readiness summary.

What's the best way to balance testing effort and risk for web application bug fixes?▼

Balance testing effort and risk by selecting tiered QA plans: Quick, Standard, or Exhaustive tiers align test depth with project needs, generating fix evidence and health scores to guide web-app releases.

Can I assess ship-readiness without automatically modifying my source code?▼

Yes, you can assess ship-readiness without modifying source code by running QA in report-only mode to evaluate web-app health, or by using plan-mode safe operations to preview fixes before applying them.

How does the atomic bug-fix loop work during web application testing?▼

The atomic bug-fix loop runs tests, commits each source code fix as an isolated atomic change, and re-verifies the web application iteratively to ensure defects are resolved without introducing regressions.

When should I use exhaustive QA testing instead of a quick test for my web app?▼

Use exhaustive QA testing instead of a quick test when preparing for high-risk web application releases, requiring maximum defect detection, detailed fix evidence, and comprehensive health score validation before shipping.