qa

Identify and validate web application bugs with tiered QA testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

Core Features & Use Cases

  • Tiered QA coverage: Quick (critical/high), Standard (+ medium), Exhaustive (+ cosmetic).
  • Regressions: before/after health scores, fix evidence, ship-readiness summaries, and support for report-only mode with /qa-only.
  • Collaboration and tooling: supports guided asks and web search for evidence.

Quick Start

Run /qa to start a quick QA pass on the current web app.

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 and fix bugs automatically?▼

To test a web app and fix bugs, run a QA pass to identify issues, iteratively fix source code, commit each fix atomically, and re-verify. This produces before/after health scores and ship-readiness summaries.

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

QA testing tiers scale coverage: Quick targets critical and high bugs, Standard adds medium severity, and Exhaustive includes cosmetic issues. Choose a tier based on required release readiness depth.

Can I generate a bug report without modifying the source code?▼

Yes, you can generate a report-only bug summary without modifying code by using the /qa-only mode. This validates bugs and produces health scores without applying atomic commits.

How do I verify release readiness for a web app before shipping?▼

Verify release readiness by running an exhaustive QA pass to identify and fix bugs across all severity levels. The process outputs a ship-readiness summary with before/after health scores and fix evidence.

Does automated QA testing support web search for bug evidence?▼

Yes, automated QA testing supports web search to gather evidence during validation. It also supports guided asks to systematically identify and verify bugs in the web application.