qa

Automate end-to-end QA testing of web applications with evidence and health scores.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often struggle to reproduce defects consistently and verify fixes across web applications. This skill provides structured, repeatable QA workflows, capturing evidence and generating before/after health scores to support release decisions.

Core Features & Use Cases

  • End-to-end UI and API testing with reproducible evidence
  • Bug reproduction, fix validation, and regression verification
  • Ship-readiness reporting with health scores and concise summaries for stakeholders

Quick Start

Run a full QA pass against the target URL and generate the before/after health report with evidence.

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 for web applications?

Automate end-to-end QA testing for web applications by executing structured workflows across UI flows, API endpoints, and integration points. This process requires a defined test plan and target URL access to perform functional verification and collect evidence for ship-readiness.

What is regression testing and how does it verify bug fixes?

Regression testing verifies bug fixes by reproducing defects and validating that new code changes do not break existing functionality. It applies structured test plans to feature branches and post-fix validation to ensure consistent web application health and generate before/after health scores.

Do I need a test plan to run regression checks on a feature branch?

Yes, a test plan is required to run regression checks on a feature branch. The test plan guides the end-to-end QA process, directing the automation across UI flows and API endpoints to capture evidence and calculate ship-readiness health scores.

Can I generate ship-readiness reports with health scores after bug reproduction?

Yes, you can generate ship-readiness reports with health scores after bug reproduction. The QA workflow captures reproducible evidence during fix validation and regression verification, producing concise summaries with before/after health scores to support release decisions for stakeholders.

What is the best way to validate API endpoints and UI flows during a new release?

The best way to validate API endpoints and UI flows during a new release is to apply structured, repeatable QA workflows. This captures reproducible evidence for functional verification and generates before/after health scores to support release decisions.