qa

Test web applications end-to-end and verify fixes with health scoring.

1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/shhubbh/flowstate --skill qa-shhubbh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/shhubbh/flowstate/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/shhubbh/flowstate --skill qa-shhubbh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing and bug-fix workflows are often fragmented across tickets, tests, and manual validation. This Skill provides a repeatable, end-to-end approach to test web apps, reproduce defects, apply atomic fixes, and re-verify outcomes.

Core Features & Use Cases

  • End-to-end QA testing that reproduces issues and validates fixes.
  • Atomic commits with before/after health checks and ship-readiness summaries.
  • Doc-ready outputs like health scores, evidence, and reports for stakeholders.

Quick Start

Run a standard QA pass on the current branch and generate a ship-readiness report.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate QA testing and bug verification for a web application?▼

QA testing for web applications is automated by reproducing defects, applying atomic fixes, and verifying outcomes end-to-end. This approach covers the full stack from UI to API and generates a ship-readiness summary with health scores.

What's the best way to structure bug-fix workflows with atomic commits?▼

The best way to structure bug-fix workflows is by enforcing atomic commits alongside before and after health checks. This process validates fixes end-to-end and produces doc-ready outputs like evidence and reports for stakeholders.

How does end-to-end test verification work across the UI and API stack?▼

End-to-end test verification works by applying regression checks across the full stack, from UI to API. It reproduces issues, validates applied fixes, and generates evidence with a ship-readiness summary to ensure release quality.

Can I generate ship-readiness reports and health scores after a regression check?▼

Yes, you can generate ship-readiness reports and health scores after a regression check. The workflow applies before and after health scoring, gathers evidence, and outputs doc-ready reports for stakeholders to ensure release quality.

Does this QA testing approach apply during feature development or only for bug hunts?▼

This QA testing approach applies during feature development, bug hunts, and regression checks. It provides a repeatable method to test web apps, reproduce defects, apply atomic fixes, and verify outcomes across the entire stack.