qa

Tests web applications in a browser, fixes found bugs with atomic commits, and re-verifies.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/bobbo01/B2BPlatform --skill qa-bobbo01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/bobbo01/B2BPlatform/tree/main/.agents/skills/gstack-qa
Command: npx skills add https://github.com/bobbo01/B2BPlatform --skill qa-bobbo01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually clicking through a web app to find bugs is slow and easy to skip, and found bugs often go unfixed or unverified. This Skill runs systematic QA testing against a running web application, fixes the bugs it finds in source code with atomic commits, and re-verifies each fix. ## Core Features & Use Cases - Tiered QA Testing: Choose Quick (critical/high severity), Standard (+ medium), or Exhaustive (+ cosmetic) coverage of pages, forms, and states. - Test-Fix-Verify Loop: Each confirmed bug gets its own atomic git commit, then is re-tested to confirm the fix actually works. - Structured Reporting: Produces before/after health scores, fix evidence, and a ship-readiness summary, with a regression mode using baseline reports. - Test Framework Bootstrap: Detects missing test infrastructure, recommends a framework for the detected runtime, and generates initial real tests plus CI configuration. - Use Case: After shipping a feature branch, run the QA workflow against your local app to catch a broken checkout form, get it fixed and committed automatically, and receive a ship-readiness report. ## Quick Start Ask the assistant to QA test the app running at your local URL and fix any bugs it finds.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automatically test my web app and fix the bugs found?

Run the QA workflow against your app's URL. It clicks through pages and forms like a real user, logs each bug by severity, fixes confirmed bugs in source code with atomic commits, and re-verifies each fix before reporting.

What QA testing tiers are available for web applications?

Three tiers exist: Quick fixes only critical and high severity issues, Standard adds medium severity, and Exhaustive also covers low and cosmetic issues. Standard is the default when no tier flag is given.

Can I run QA testing without specifying a URL?

Yes. On a feature branch with no URL given, the workflow enters diff-aware mode and scopes testing to the changes on your branch. Otherwise a target URL such as a localhost address is required.

Why does the QA workflow refuse to start with uncommitted changes?

It requires a clean git working tree so every bug fix lands as its own atomic commit. You can choose to commit or stash existing changes first, or abort and clean up manually.

Does the QA workflow set up a test framework if my project has none?

Yes. It detects the project runtime, researches current framework best practices, asks you to confirm a choice, installs and configures it, writes initial real tests, and can add a GitHub Actions CI workflow.

What are the limitations of automated browser QA testing?

It depends on the browse binary being built and reachable, and CDP mode is needed to reuse your real browser's auth sessions. It verifies fixes it makes but cannot guarantee coverage of every possible user path.