qa

Execute defined QA test plans and record results with evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic QA testing helps teams verify web applications by running structured tests and capturing evidence of outcomes.

Core Features & Use Cases

  • End-to-end QA coverage across features, fixes, and regressions
  • Generates before/after health scores, fix evidence, and ship-readiness summaries
  • Supports both full-app QA and diff-focused verification on changed components

Quick Start

Run the qa workflow on the current project to start automated testing, bug fixing, and verification.

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 my web application?

Automated QA testing executes defined test plans on web applications to discover bugs, record results with evidence, and verify fixes. It supports full-app checks and diff-focused verification on changed components.

What is a ship-readiness summary and how does it work with web app health scores?

A ship-readiness summary evaluates web app release readiness by comparing before and after health scores. It documents critical, high, medium, and low-severity issues across workflows with reproducible steps and fix evidence.

Can I run diff-focused QA checks only on changed components instead of the full app?

Yes, diff-focused QA checks target changed components specifically rather than running full-app tests. This approach verifies fixes and regressions efficiently by executing test plans scoped to modified workflows.

How do I document bug fixes with reproducible steps and evidence during testing?

QA testing documents bug fixes by executing test plans, recording outcomes with evidence, and capturing reproducible steps. It generates before and after health scores alongside a ship-readiness summary for verification.

Does this QA testing approach cover critical, high, medium, and low-severity issues?

Yes, QA testing covers critical, high, medium, and low-severity issues across application workflows. It systematically discovers and verifies bugs while producing evidence and health scores for each severity level.

What is the best way to verify bug fixes and generate evidence for a web application release?

Run structured QA testing to verify bug fixes by executing test plans across affected workflows. It captures evidence, generates before and after health scores, and produces a ship-readiness summary for release validation.