qa

Automate web application QA testing with tiered test suites and health scoring.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/abhishekmmgn/didactic-invention --skill qa-abhishekmmgn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/abhishekmmgn/didactic-invention/tree/main/.agents/skills/gstack/qa
Command: npx skills add https://github.com/abhishekmmgn/didactic-invention --skill qa-abhishekmmgn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing accelerates finding defects in a web application, reduces manual debugging time, and ensures releases meet quality goals.

Core Features & Use Cases

  • End-to-end QA passes across core user journeys, UI validation, and regression suites.
  • Iterative bug fixing with atomic commits and re-verification until health metrics improve.
  • Generates before/after health scores, evidence of fixes, and a ship-readiness summary for release decisions.
  • Use Case: When a feature lands, run QA, log defects, fix them in small commits, and revalidate until the app ships confidently.

Quick Start

Run a quick QA pass on the current app, identify defects, commit fixes, and re-run tests until acceptance criteria are met.

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?

Automated QA testing identifies regression issues in web applications by running tiered test suites across core user flows, UI behavior, performance, and accessibility, reducing manual debugging effort through iterative defect logging and fix re-verification.

What is a web app health score and how does it track bug fixes?

A web app health score quantifies release readiness by evaluating test pass rates across core user flows. QA testing generates before and after health scores with evidence of fixes, providing a ship-readiness summary to validate that regression issues are resolved.

How do I fix UI defects and verify them without manual debugging?

You fix UI defects by running a QA pass to identify issues, committing fixes in small atomic commits, and re-running tests to re-verify after each change. This iterative regression testing continues until acceptance criteria are met and the web app ships confidently.

Can I run different levels of QA testing based on my project needs?

Yes, QA testing offers quick, standard, and exhaustive test tiers applied to core user flows and UI behavior. You select the appropriate regression testing tier to match specific project requirements, scaling coverage from basic validation to comprehensive accessibility and performance checks.

What's the best way to ensure ship-readiness before a web app release?

The best way to ensure ship-readiness is running an exhaustive QA pass that generates a summary of release readiness. This process validates core user journeys, logs remaining defects, applies atomic commits for bug fixes, and re-verifies until health scores confirm the web app is ready to ship.