qa

Name: qa
Availability: InStock
Author: ligianehua

Test web applications end-to-end and fix defects with atomic commits.

Updated Mar 30, 2026

Search Tags:#automation #testing #qa #reporting #end-to-end #bug-fix #web-app

Ready to run

npx skills add https://github.com/ligianehua/Gstack --skill qa-ligianehua

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing and bug-fix cycles are time-consuming and error-prone without a repeatable process. This skill orchestrates end-to-end testing, automated verification, and atomic fixes to help teams ship reliable software.

Core Features & Use Cases

Systematic end-to-end web app testing
Atomic commits for each bug fix and re-verification
Health score and ship-readiness reporting
Tiered testing: Quick, Standard, Exhaustive
Automated report generation and evidence

Quick Start

Run a QA pass on your target web app, fix issues atomically, and re-verify to confirm the fixes.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I automate end-to-end web app testing and bug fixing?▼

Automated end-to-end web app testing applies structured steps to find defects, fix them atomically, and re-verify. This process uses tiered testing cycles to systematically resolve bugs and produce ship-readiness summaries.

What is the best way to structure QA reporting for a web application?▼

QA reporting for a web application should generate structured documents containing health scores, evidence collection, and ship-readiness summaries. This provides clear before-and-after metrics to verify code stability after bug fixes.

Can I run a quick QA test pass without an exhaustive testing cycle?▼

You can run a Quick QA test pass instead of an exhaustive cycle. The testing process supports defined tiers—Quick, Standard, and Exhaustive—allowing you to match the depth of testing to your immediate shipping needs.

How does atomic bug fixing improve software ship-readiness?▼

Atomic bug fixing improves ship-readiness by isolating each code fix into an individual commit. This is followed by automated re-verification to confirm the defect is resolved, ensuring stable and clean code progression.

What do I need to generate before and after health scores for my codebase?▼

Generating health scores requires running a structured QA pass across your codebase. The process evaluates testing tiers, collects evidence, and outputs before and after scores to quantify improvements from bug fixes.

Why use tiered testing cycles for QA automation instead of a single test run?▼

Tiered testing cycles prevent unnecessary testing overhead by offering Quick, Standard, and Exhaustive levels. This structures QA automation to match the required verification depth, efficiently balancing bug-fix speed and ship-readiness.