qa

Run tiered QA checks and verify bug fixes with before/after health scores.

Updated May 7, 2026
One-click install
npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill qa-tumeloramaphosa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/TumeloRamaphosa/StudEx-Valley-OS/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/TumeloRamaphosa/StudEx-Valley-OS --skill qa-tumeloramaphosa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA catches broken flows, UI regressions, console errors, and performance or accessibility issues before users hit them. The qa skill not only runs tests, it fixes verified bugs one-by-one and re-verifies after each atomic change so regressions do not sneak back in.

Core Features & Use Cases

  • Tiered QA coverage (Quick / Standard / Exhaustive): Run critical and high issues first, then expand to medium and finally cosmetic checks when you want deeper confidence.
  • Before/after health scoring with evidence: Produces a health score summary plus “before vs after” evidence to show what improved.
  • Iterative fix-and-verify loop with atomic commits: Finds an issue, applies a contained fix, commits it atomically, and re-runs QA to confirm the bug is truly resolved.
  • Report-only option via /qa-only: Generates QA findings without changing code when you only want visibility.

Quick Start

Ask the agent to qa test this site to run QA and fix the bugs it finds, then return a ship-readiness summary.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run regression testing and automatically fix web application bugs?

Systematic QA testing finds broken flows and UI regressions, applies contained bug fixes with atomic commits, and re-runs verification to ensure the issue is resolved without introducing new regressions.

Can I generate a QA report on console errors and accessibility issues without modifying my code?

Yes, you can generate a QA report without changing code by running a report-only QA check, which produces evidence-backed findings on console errors and accessibility issues for visibility rather than automatic fixes.

What is the best way to verify web application health before and after deploying bug fixes?

Health scoring verifies web application health by running systematic checks before fixes are applied, then scores health again afterward to produce a summary showing the before and after health delta.

Does iterative bug fixing with atomic commits prevent regressions from sneaking back into web app testing?

Iterative bug fixing applies a contained fix for each issue, commits it atomically, and re-runs QA checks to verify the bug is truly resolved, preventing regressions from reappearing in web app testing.

How do I test web app interactions and UI states to ensure ship-readiness?

Tiered QA coverage tests web app interactions, UI states, and links by running critical and high issues first, then expanding to medium and cosmetic checks to produce a final ship-readiness summary.

When should I not use automated QA testing for web applications?

You should avoid automated QA testing when you only want visibility into issues without code changes, or if your product workflow does not support iterative commits and regression testing for web applications.