qa

Run tiered QA tests on web applications and commit atomic bug fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA testing and iterative bug fixing of a web application. 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". Three tiers: Quick (critical/high only), Standard, Exhaustive. Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only. Voice triggers: "quality check", "test the app", "run QA".

Core Features & Use Cases

  • Systematic QA runs across web applications with tiered scopes
  • Atomic bug fixes and re-verification with ship-readiness reporting
  • Voice triggers and report-only modes for flexible QA workflows

Quick Start

Trigger the QA workflow on your app by running /qa and follow the prompts to begin testing.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run automated QA testing and fix bugs in a web application?

Automated QA testing and bug fixing for a web application involves running systematic tests, iteratively fixing source code bugs atomically, and re-verifying to produce a ship-readiness summary. Use /qa to trigger this workflow and follow the prompts.

Can I generate a QA health score report without automatically applying code fixes?

Yes, you can generate a report-only QA health score by using the /qa-only mode. This evaluates the web application's health, records before scores, and identifies issues without committing atomic bug fixes to the source code.

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

QA testing tiers differ in scope: Quick focuses on critical and high-priority issues only, Standard provides balanced coverage, and Exhaustive performs a comprehensive evaluation across the entire codebase to ensure complete ship-readiness.

Does the QA testing workflow support voice triggers for hands-free operation?

Yes, the QA workflow supports voice-based triggers to streamline operations. You can initiate testing by using phrases like "quality check", "test the app", or "run QA" to start the automated bug fixing process.

What is the best way to verify bug fixes before shipping a web app?

The best way to verify bug fixes is through an atomic commit and re-verification process. This QA workflow records each fix, produces before and after health scores, and generates a ship-readiness summary based on deterministic testing.

Are there any dependencies required to run systematic web app testing and bug fixing?

No specific dependencies are required to run systematic web app testing and bug fixing. The workflow operates independently to orchestrate deterministic testing, record atomic fixes, and generate health scores across your codebase.