qa

Test web applications and fix bugs with atomic commits and evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA engineers and developers can systematically test a web application, identify issues, and fix them with atomic commits, ensuring traceable improvements.

Core Features & Use Cases

  • End-to-end testing across navigation, forms, and state changes
  • Evidence-backed fixes with before/after screenshots or logs
  • Structured QA reports including health indicators and regression checks

Quick Start

Describe the target URL and scope, run the QA workflow, then review the before/after evidence and re-run tests to verify fixes.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I fix bugs in a web application through structured QA testing?

You fix bugs in a web application by running structured QA testing across setup, navigation, forms, and state changes, applying fixes through atomic commits, and generating before/after evidence to verify the results.

What is end-to-end QA testing with before/after evidence?

End-to-end QA testing with before/after evidence is a process that identifies bugs across navigation and state changes, fixes them with atomic commits, and captures screenshots or logs to re-verify the fixes.

How do I generate a QA report with health signals and regression checks?

To generate a QA report with health signals and regression checks, test the target URL across setup, navigation, forms, and state changes, then compile the before/after evidence into a structured health summary.

Can I automate regression checks for state changes and forms on a target URL?

Yes, you can automate regression checks for state changes and forms on a target URL by running structured QA testing, applying atomic commits for bug fixes, and re-verifying the fixes using captured evidence.

What is the best way to ensure traceable improvements when fixing web application bugs?

The best way to ensure traceable improvements when fixing web application bugs is to implement atomic commits alongside structured QA testing, producing before/after evidence and a clear plan for regression checks.

Does structured QA testing work for web applications with complex form validation and state changes?

Yes, structured QA testing works for web applications with complex form validation and state changes by systematically testing these areas, applying atomic commits for fixes, and re-verifying the results with evidence.