qa

Test web applications systematically and fix bugs with atomic commits.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Andy-HNU/AndyClaw --skill qa-andy-hnu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/Andy-HNU/AndyClaw/tree/main/skills/gstack-qa
Command: npx skills add https://github.com/Andy-HNU/AndyClaw --skill qa-andy-hnu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

QA testing of web applications can be tedious and error-prone; this skill provides a structured, repeatable approach to find bugs and verify fixes.

Core Features & Use Cases

  • Systematic QA testing of web apps with quick, standard, and exhaustive tiers.
  • Iterative bug fixing with atomic commits, re-verification, and evidence like health scores and ship-readiness summaries.
  • Proactive guidance on when features are ready for testing and support for report-only mode.

Quick Start

Invoke the qa workflow on your site by specifying the target URL and QA tier, then run the automated test-fix-verify cycle.

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 and bug fixing for my web application?▼

Automated QA testing for a web app runs a test-fix-verify cycle to identify bugs, apply atomic commits, and re-verify fixes. It produces health scores and ship-readiness summaries to ensure deployment quality.

What is the difference between quick, standard, and exhaustive e2e testing tiers?▼

E2e testing tiers scale the depth of bug detection. Quick, standard, and exhaustive tiers systematically increase test coverage, generating before and after health scores to gauge web app stability.

Can I run a report-only QA test without automatically fixing the bugs?▼

Yes, you can run a report-only QA test by invoking the /qa-only mode. This evaluates the web app, identifies bugs, and generates health scores and ship-readiness summaries without applying atomic commits or fixes.

How do I verify bug fixes with atomic commits during web app testing?▼

Verifying bug fixes during web app testing involves applying atomic commits for each fix and then running re-verification. This systematic process ensures each bug is resolved without introducing regressions.

Does automated QA testing tell me when my web app features are ready to ship?▼

Automated QA testing provides a ship-readiness summary based on before and after health scores. This evaluation determines if your web app features have passed the necessary bug-fix and re-verification thresholds for deployment.