qa

Test web applications across three tiers and fix bugs with atomic commits.

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

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. Proactively suggest when the user says a feature is ready for testing or asks "does this work?". 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

  • Systematic QA testing workflow to identify bugs and verify fixes across a web application.
  • Atomic commits for each bug fix with re-verification and a ship-readiness summary.
  • Tiered QA modes: Quick, Standard, Exhaustive to fit different time budgets.
  • Output includes health scores, fix evidence, and a comprehensive QA report.
  • Supports report-only mode for non-intrusive verification.

Quick Start

Run a QA cycle on the target URL to systematically test, fix, and re-verify the site until ship-readiness is achieved.

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 the bugs found?

Systematic QA testing for a web application runs test cycles, iteratively fixes discovered bugs in source code with atomic commits, and re-verifies the site. This process uses a target URL and defined scope to generate before/after health scores and a ship-readiness summary.

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

QA testing tiers differ by bug severity scope. Quick testing covers critical and high severity issues, Standard adds medium severity, and Exhaustive includes cosmetic issues. Each tier produces fix evidence and a ship-readiness summary to match your available time budget.

Can I run a non-intrusive QA test on a web app without modifying the source code?

You can run non-intrusive QA testing using the report-only mode. This mode systematically verifies the web application and produces health scores and a comprehensive QA report without applying any atomic commits or bug fixes to the source code.

What do I need to provide to start a QA testing cycle on my web app?

To start a QA testing cycle, you need to provide a target URL and a defined testing scope. You can also supply optional authentication credentials or test data to ensure the web application can be fully accessed and systematically verified.

How are bug fixes verified during the QA testing process?

Bug fixes are verified through atomic commits. Each time a bug is fixed in the source code, the system commits the fix atomically and re-verifies the web application, ultimately providing before/after health scores and comprehensive fix evidence.