qa

Identify web application defects through tiered QA testing and structured reporting.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/TwoToned/gearflow --skill qa-twotoned
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/TwoToned/gearflow/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/TwoToned/gearflow --skill qa-twotoned

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing for web applications is time-consuming and error-prone; systematic QA ensures issues are caught early and fixes are reproducible.

Core Features & Use Cases

  • Systematically QA test a web application to identify defects across UI, functionality, and performance.
  • Iteratively fix bugs in source code, committing each fix atomically and re-verifying to ensure stability.
  • Produce before/after health reports, fix evidence, and ship-readiness summaries to communicate quality.
  • Supports multiple tiers (Quick, Standard, Exhaustive) to balance speed and thoroughness.

Quick Start

Run a quick smoke test on the current web app and report any failing critical paths.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I systematically test a web application for defects?

Systematically test a web application by applying a tiered QA approach (Quick, Standard, Exhaustive) to identify UI, functionality, and performance defects, generating structured reports with health scores and evidence.

How do I automate bug fixes and ensure release-readiness?

Automate bug fixes iteratively by committing each fix atomically to the source code and re-verifying the application to ensure stability and release-readiness.

Can I run a quick smoke test on my web app?

Yes, you can run a Quick tier smoke test on your web app to rapidly report any failing critical paths and assess basic ship-readiness without exhaustive overhead.

What is the best way to report quality assurance results?

Report quality assurance results by producing before and after health reports, fix evidence, and ship-readiness summaries to clearly communicate application quality and stability.

What is the difference between Quick, Standard, and Exhaustive testing tiers?

The Quick, Standard, and Exhaustive testing tiers balance speed and thoroughness, scaling from rapid critical path checks to comprehensive defect identification across the web application.

When should I use exhaustive QA testing over a quick check?

Use Exhaustive QA testing over a quick check when you need maximum thoroughness to deeply identify UI, functionality, and performance defects before a critical web application release.