qa

Run structured QA passes on web applications and verify fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing a web application is time-consuming and error-prone without a repeatable process. This skill provides a structured approach to identifying defects, validating fixes, and ensuring release readiness, reducing cycle time and risk.

Core Features & Use Cases

  • Structured QA passes: plan, execute, and report defects across critical paths and user flows.
  • Iterative fix-and-verify loop: fix bugs in source code, commit each change atomically, and re-run tests to verify until green.
  • Ship-readiness & health scoring: generate before/after health scores and a ship-readiness summary to support release decisions.
  • Tiers for depth: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic) QA to balance speed and thoroughness.
  • Real-world scenario: imagine a login flow failing under a specific browser; use this skill to reproduce, fix, and verify end-to-end.

Quick Start

Run a full QA pass on the current web app, fix all confirmed issues, commit each fix atomically, and re-run QA to confirm closure.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I systematically QA test a web app to identify defects?

Structured QA testing plans, executes, and reports defects across critical paths and user flows. It applies across development cycles to catch issues early and produce ship-readiness summaries.

Can I automate bug fixing and verification in a single workflow?

Yes, you can automate bug fixing and verification through an iterative loop that fixes source code, commits each change atomically, and re-runs tests to verify closure.

Does this QA testing process provide a ship-readiness summary?

Yes, the QA testing process generates before and after health scores alongside a ship-readiness summary to support your release decisions and verify defect closure.

What is the best way to balance speed and thoroughness during web app testing?

The best way to balance testing speed and thoroughness is using depth tiers: Quick for critical defects, Standard for medium issues, and Exhaustive for cosmetic bugs.

Are there limitations to automated web app verification?

Automated web app verification focuses on critical paths, user flows, and source code fixes. Cosmetic issues require an Exhaustive tier pass, while complex browser-specific edge cases need targeted reproduction.