qa

Test web applications, report defects, and iteratively fix them with health scores.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual QA of web applications is slow and error-prone. This Skill systematically QA tests a web application, reports defects, and iteratively fixes them, committing each fix atomically and re-verifying. Three tiers—Quick, Standard, and Exhaustive—guide coverage and effort, while structured outputs help teams measure quality and readiness. This Skill supports plan-mode use, including a dedicated /qa-only mode, and voice triggers to run QA on demand.

Core Features & Use Cases

  • Systematic QA testing of a web application and iterative bug fixes with atomic commits.
  • Tiered coverage: Quick (critical/high), Standard (plus medium), Exhaustive (cosmetic) to match risk tolerance.
  • Rich outputs: before/after health scores, fix evidence, and a ship-readiness summary.
  • Integration with plan-mode prompts and dedicated QA commands (e.g., /qa-only) for repeatable workflows.
  • Voice and text triggers: run QA via natural language or commands like "qa test this" or "find bugs on site".

Quick Start

Ask me to run a QA pass on your site and I will start tests, report results, fix bugs, and re-run verification.

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?

Automate regression testing by running a systematic QA pass that tests a web app, reports defects, and iteratively fixes them with atomic commits. The process applies to manual QA tasks and bug-fix cycles, re-verifying after each fix to ensure stability.

What is ship-readiness assessment and when do I need it for web apps?

Ship-readiness assessment is a summary produced after QA testing a web app to measure quality and release readiness. You need it before deploying web apps to verify that defects are fixed and health scores meet your risk tolerance.

How do I run a quick QA test on my site to find bugs?

Run a quick QA test by triggering it via natural language or commands like "qa test this" or "find bugs on site". The Quick tier covers critical and high-severity issues, reporting defects and fix evidence efficiently.

Can I use automated QA for manual testing tasks across web services?

Yes, automated QA applies to manual QA tasks, regression testing, and bug-fix cycles across web apps and services. It produces before/after health scores and integrates with plan-mode prompts for repeatable workflows without requiring manual intervention.

What is the best way to fix bugs iteratively before deploying a web app?

The best way to fix bugs iteratively is using a systematic QA cycle that tests the web app, reports defects, and commits each fix atomically before re-verifying. This approach provides fix evidence and a ship-readiness summary for confident deployment.

Does automated QA support different levels of test coverage based on risk tolerance?

Automated QA supports tiered coverage to match risk tolerance: Quick for critical/high issues, Standard for medium severity, and Exhaustive for cosmetic defects. This guides testing effort and coverage scale across web applications.