qa

Test and verify web applications, fix bugs with atomic commits, and re-verify.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates QA testing and iterative bug-fixing for web applications, shortening feedback cycles and improving release confidence.

Core Features & Use Cases

  • Tiered QA workflows: Quick (critical/high), Standard, and Exhaustive tests to tailor coverage.
  • Evidence and health reporting: Before/after health scores, bug evidence, and ship-readiness summaries.
  • Structured reporting: Generates QA report templates and enables atomic commits for fixes.

Quick Start

Run the QA workflow against the target app to start testing, fixing, and re-verifying.

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 a web application?

You can automate QA testing by running tiered workflows against your web application, which identifies bugs, applies atomic commits for fixes, and re-verifies to produce health scores and ship-readiness summaries.

What is a health score in web app QA reporting?

A health score in QA reporting measures web application stability before and after testing cycles. It pairs with bug evidence and a ship-readiness summary to quantify release confidence and track improvements.

How do I choose between Quick, Standard, and Exhaustive QA testing tiers?

Choose Quick QA testing for critical and high-priority bugs, Standard for routine coverage, or Exhaustive for maximum testing depth. This tiered approach tailors feedback cycles and reporting to match your release timeline.

Does automated QA testing work without external dependencies?

Automated QA testing operates with zero external dependencies, running workflows directly against your web application. It handles testing, bug fixing, and report generation entirely within its own environment.

What's the best way to structure bug fix commits during QA testing?

The best way to structure bug fix commits during QA testing is using atomic commits. This isolates each fix individually, ensuring clear tracking before re-verifying the web application and updating the health score.