qa

Run tiered QA workflows on web applications and generate ship-readiness summaries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA workflow systematically tests a web application, captures evidence of issues, and guides iterative bug fixes with re-verification so you can ship what actually works.

Core Features & Use Cases

It helps you run structured QA passes (Quick, Standard, Exhaustive) and produce before/after health scores plus a ship-readiness summary. It focuses on scenarios like “does this work?”, “test the site”, “find bugs”, and “fix what's broken”, including a report-only mode for /qa-only. It’s designed to support the fix loop by verifying each change atomically, reducing the chance you fix one thing and break another.

Quick Start

Ask for a full QA run and say the tier you want, for example: “Run QA for this app in Standard mode and fix all bugs you find.”

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run regression verification to find bugs in my web application?▼

You can run a full QA pass by specifying a tier, such as Standard or Exhaustive mode. The workflow tests the site, finds bugs, applies atomic fixes, and re-verifies each change to prevent breaking existing functionality.

Can I generate test evidence without automatically fixing the issues?▼

Yes, you can use a report-only mode triggered by a /qa-only request to generate test evidence and health scores without applying fixes. This allows you to review the defects and ship-readiness summary before making any code changes.

What is the difference between Quick, Standard, and Exhaustive QA testing tiers?▼

The testing tiers dictate the depth of your QA pass. Quick, Standard, and Exhaustive modes execute structured testing at varying coverage levels, producing before and after health scores to measure ship readiness.

How do atomic bug fixes prevent new issues during web testing?▼

Atomic bug fixes isolate and verify each change individually during web testing. This fix loop verifies modifications one by one, reducing the chance that fixing one defect breaks another feature in the application.

Does this QA workflow require any specific testing dependencies or frameworks?▼

No specific testing dependencies or frameworks are required. The workflow uses allowed tools to inspect and validate changes directly, generating test evidence and health score deltas without external component setup.