qa

Test web applications end-to-end and iteratively fix bugs with health scores.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA engineers and developers waste time repeatedly finding and fixing bugs in web apps. This skill provides an automated, end-to-end QA loop that tests, confirms fixes, and documents evidence to speed up shipping.

Core Features & Use Cases

  • End-to-end QA testing of web applications with repeatable, atomic fixes and verifications.
  • Three-tier QA: Quick, Standard, Exhaustive, with health scores and ship-readiness summaries.
  • Proactive prompts and evidence-driven reporting to inform release decisions.

Quick Start

Describe what you're building and run /qa to start the automated test-and-fix loop.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate end-to-end QA testing and bug fixing for a web app?

Automated end-to-end QA testing runs a continuous test-and-fix loop on your web app, iteratively committing bug fixes while generating health scores and ship-readiness summaries. You describe your application and trigger the process to start.

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

Quick, Standard, and Exhaustive QA tiers represent increasing levels of testing depth for web applications. Each tier produces before-and-after health scores and ship-readiness summaries across functional, UI, and performance aspects to inform your release decisions.

Can I verify UI and performance issues automatically during web app QA?

You can verify UI and performance issues automatically during web app QA. The process evaluates functional, UI, and performance aspects, producing fix evidence and a comprehensive ship-readiness summary to confirm your application is ready for release.

Does automated QA testing work without external testing dependencies?

Automated QA testing works without external dependencies, relying on standard development tools like Bash, Read, Write, Edit, Glob, Grep, and WebSearch. It loads internal preamble logic and telemetry to execute the end-to-end test and fix loop.

How do I document bug fix evidence for release readiness?

Document bug fix evidence by running an automated QA loop that commits each change individually. The process generates before-and-after health scores, fix evidence, and a ship-readiness summary across functional, UI, and performance aspects to support release decisions.