qa

Automate QA testing of web applications and iteratively fix bugs.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/zhu637882-stack/jiaoyi --skill qa-zhu637882-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/zhu637882-stack/jiaoyi/tree/main/qoder-config-backup/skills/gstack-qa
Command: npx skills add https://github.com/zhu637882-stack/jiaoyi --skill qa-zhu637882-stack

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", or "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. (gstack)

Core Features & Use Cases

  • Tiered QA workflows: Quick, Standard, and Exhaustive with progressive depth and reporting.
  • Iterative fixes & verification: commits each fix atomically, re-runs tests to confirm closure.
  • Ship-readiness reporting: outputs before/after health scores, evidence of fixes, and a ship-readiness summary.
  • Use Case: when a feature is ready for validation, run QA to surface defects, verify fixes, and prepare a deployment decision.

Quick Start

Run QA on the target site, capture before/after health scores, and verify fixes before deployment.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate regression testing for a web application to find bugs before shipping?

Automated QA testing systematically surfaces defects across critical paths and workflows in a web application. It runs tiered test suites, iteratively fixes bugs in source code, and re-verifies fixes before producing a ship-readiness summary.

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

Quick QA testing targets critical and high-severity defects only, Standard adds medium-severity issues, and Exhaustive includes cosmetic defects. Each tier progressively increases testing depth to match your validation needs before deployment.

Do I need baseline test data to run QA testing on my web application?

Yes, comprehensive QA testing requires access to the application environment and baseline test data. This setup allows the process to accurately execute tests against critical paths, iteratively fix bugs, and verify closures.

Can I run QA testing to generate a health score report without modifying my source code?

Yes, you can use a report-only mode to run QA testing without applying fixes. This evaluates the web application, captures the health score, and surfaces defects across workflows without committing any code changes.

How does iterative bug fixing work during web application QA testing?

Iterative QA testing finds a bug, fixes it in the source code, and commits each fix atomically. It then re-runs tests to confirm the fix is verified and closed before moving to the next defect, ensuring evidence-backed closure.

When should I use automated QA testing instead of manual testing for my web application?

Automated QA testing is ideal for iterative development cycles where features need rapid validation before shipping. It systematically surfaces defects across workflows, verifies fixes, and outputs a ship-readiness summary for deployment decisions.