qa

Identify and fix web application defects through tiered end-to-end QA testing.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/uzumaki-inc/uzustack --skill qa-uzumaki-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/uzumaki-inc/uzustack/tree/main/_upstream/gstack/qa
Command: npx skills add https://github.com/uzumaki-inc/uzustack --skill qa-uzumaki-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA teams struggle to consistently identify defects across a web app and verify fixes before release.

Core Features & Use Cases

  • End-to-end testing across web applications with tiered scopes (Quick, Standard, Exhaustive)
  • Before/after health scoring, evidence collection, and ship-readiness summaries
  • Report-only mode (/qa-only) to validate results without triggering actions

Quick Start

Ask Claude Code to run a standard QA pass on your web app and return a bug-fix plan.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I find and fix bugs in a web application before release?

Systematic QA testing identifies and fixes defects in web applications through end-to-end testing scenarios. It produces a ship-readiness summary with before/after health scores and evidence of fixes to verify release readiness.

Can I run quality assurance testing without automatically applying bug fixes?

Yes, you can use the report-only mode to validate test results without triggering any fix actions. This mode performs the standard quality assurance testing and generates the health score report without modifying the application.

What is the best way to verify bug fixes are reproducible across a web app?

Tiered end-to-end QA testing enforces reproducible test results and collects evidence of fixes. By comparing before/after health scores, you can verify that bug fixes are reproducible and effective across the web application.

Does end-to-end testing support different scopes for quick checks versus exhaustive passes?

End-to-end testing supports three tiered scopes: Quick, Standard, and Exhaustive. This allows you to adjust the quality assurance depth based on your needs, from rapid validations to comprehensive ship-readiness summaries.

What limitations should I consider when using tiered QA testing for ship readiness?

Tiered QA testing targets end-to-end scenarios specifically on web applications. It requires producing before/after health scores and evidence of fixes, meaning it may not suit non-web platforms or contexts lacking reproducible test results.

How do I get a bug-fix plan after running a standard QA pass?

Ask Claude Code to run a standard QA pass on your web application. The systematic quality assurance testing will identify defects and return a structured bug-fix plan with ship-readiness summaries and health scores.