qa

Name: qa
Availability: InStock
Author: concept2cure

Test web applications, identify defects, and document fixes with health scores.

1|Updated Nov 13, 2025

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

Ready to run

npx skills add https://github.com/concept2cure/ClinicalSageAI-2-replit --skill qa-concept2cure

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA teams spend cycles manually testing web apps, chasing flaky bugs, and coordinating fixes. This Skill provides a repeatable QA workflow that catches regressions early and validates changes through structured testing and documented fixes.

Core Features & Use Cases

End-to-end QA cycles for web applications with clear pass/fail criteria.
Three-tier coverage: Quick, Standard, Exhaustive, with health scores and ship-readiness summaries.
Atomic commit workflow: each bug fix is committed separately and re-verified to ensure traceability.
Use Case: When shipping a feature, run QA, fix blockers, then verify the feature is production-ready.

Quick Start

Run the QA plan on the current branch to begin testing and verify fixes.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I automate web application testing and bug fixing before a release?▼

Automated QA testing systematically evaluates a web application to identify defects, apply fixes, and document ship readiness. It uses atomic commits for each bug fix and re-verifies the application to ensure traceability and validate production readiness.

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

QA testing tiers provide varying levels of coverage depth, from Quick basic checks to Exhaustive full validation. Each tier reports before and after health scores, fix evidence, and ship-readiness summaries to match the required validation rigor for the feature branch.

How do I verify ship readiness for a feature branch before deploying?▼

Verify ship readiness by running a QA cycle on the feature branch to evaluate pass/fail criteria. The process generates health scores and a ship-readiness summary, ensuring all blockers are fixed and re-verified through atomic commits before production deployment.

How do I ensure traceability when fixing bugs during web app QA?▼

Ensure traceability by using an atomic commit workflow where each bug fix is committed separately. The QA process logs outcomes and re-verifies each fix, documenting the evidence needed to track changes from defect identification through final resolution.

Can I run QA cycles on a feature branch without affecting the main codebase?▼

Yes, QA cycles are designed to test feature branches independently. This isolates the verification process, allowing you to catch regressions early, document fixes, and confirm ship readiness without impacting the stability of the main codebase.

Why do I need to re-verify bug fixes after committing them?▼

Re-verifying bug fixes after committing ensures that the applied changes actually resolve the defect without introducing new regressions. This validation step updates the application's health score and confirms the overall ship readiness of the feature branch.