qa

Test web applications end-to-end, fix bugs with atomic commits, and generate QA reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.

Core Features & Use Cases

  • End-to-end QA testing that mimics real user interactions
  • Atomic commits for each bug fix and re-verification
  • Proactive guidance on test readiness and feature validation
  • Ship-readiness reporting with health scores and evidence

Quick Start

Ask the QA skill to start testing your app by saying 'qa' or '/qa'.

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 web app testing and fix bugs in one workflow?

End-to-end web app testing mimics real user interactions by clicking flows and validating states to detect bugs. It coordinates automated fixes and re-verification with atomic commits across the codebase, outputting a structured QA report with before and after evidence.

What is ship-readiness reporting in QA testing?

Ship-readiness reporting in QA testing provides before and after health scores alongside fix evidence. It summarizes whether your web application is ready for release after iteratively fixing bugs in the source code and re-verifying the changes.

How do I run a quick QA test on my web application?

To run a quick QA test, simply ask the QA skill to start testing your app by saying 'qa' or '/qa'. The quick tier specifically tests for critical and high severity bugs, while standard and exhaustive tiers cover medium and cosmetic issues.

Can I use automated QA testing to commit bug fixes across my codebase?

Yes, automated QA testing iteratively fixes bugs in source code by committing each fix atomically. It then re-verifies the application to ensure the bug fix works, producing before and after evidence in a structured health score report.

What is the difference between quick, standard, and exhaustive QA testing tiers?

Quick QA testing covers only critical and high severity bugs, the Standard tier adds medium severity bugs, and the Exhaustive tier includes cosmetic issues. All tiers produce health scores, fix evidence, and a ship-readiness summary.

Does automated QA testing work without setting up external test dependencies?

Yes, automated QA testing works without external dependencies. It tests web applications like a real user by clicking flows and validating states directly, requiring no additional test frameworks to detect and fix bugs.