qa

Test web applications end-to-end, detect regressions, and fix bugs with atomic commits.

Updated Aug 23, 2026

Search Tags:#automation #testing #qa #regression #bug-fix #web-app

Ready to run

npx skills add https://github.com/caraseli02/MoldovaDirect --skill qa-caraseli02

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/caraseli02/MoldovaDirect/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/caraseli02/MoldovaDirect --skill qa-caraseli02

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA tests your web application end-to-end, detects regressions, and fixes bugs by committing each change atomically.

Core Features & Use Cases

Provides guided QA workflows with Quick, Standard, and Exhaustive tiers, producing before/after health scores, fix evidence, and a ship-readiness summary.
Iteratively fixes bugs in source code with atomic commits and re-verification to ensure changes behave as expected.
Proactively suggests QA directions when asked whether a feature is ready for testing or needs deeper QA.

Quick Start

Run the QA workflow on your project to automatically test, fix, and re-verify the latest changes.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I automate end-to-end QA testing and fix regressions in my web application?▼

End-to-end QA testing and regression fixing are automated by running a workflow that tests your web application, detects regressions, applies atomic source code commits, and re-verifies the outcomes to ensure changes behave as expected.

What is the difference between quick, standard, and exhaustive QA testing scopes?▼

Quick, standard, and exhaustive QA scopes provide different levels of testing depth for your web application, generating before and after health scores, fix evidence, and a final ship-readiness summary based on the chosen tier's coverage.

Does automated bug fixing require a browser automation framework to run tests?▼

Automated bug fixing requires a browser automation framework and code access to execute tests, apply source fixes iteratively, and verify outcomes, documenting all evidence within a structured QA report.

How do I know if my web application feature is ready for regression testing?▼

Regression testing readiness is evaluated by proactively suggesting QA directions when asked whether a feature needs testing, determining ship-readiness through health scores and structured fix evidence.

What's the best way to document fix evidence after detecting web app regressions?▼

Fix evidence is documented automatically by committing each change atomically during the regression fixing process, producing before and after health scores and a ship-readiness summary within a structured QA report.