qa

Run tiered QA tests on web applications and commit fixes atomically.

Updated Aug 23, 2026

Search Tags:#automation #testing #qa #verification #bug-fix #ship-readiness

Ready to run

npx skills add https://github.com/effiraid/reflix-nextjs --skill qa-effiraid

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/effiraid/reflix-nextjs/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/effiraid/reflix-nextjs --skill qa-effiraid

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 a feature is ready for testing or people ask "does this work?".

Core Features & Use Cases

Tiered QA workflows (Quick, Standard, Exhaustive) that produce before/after health scores, fix evidence, and a ship-readiness summary.
Atomic commits and automated verification loops to ensure fixes are verifiable.
Proactive guidance and evidence-driven reporting to confirm readiness for shipping.

Quick Start

Run /qa on your app to start automated QA testing, bug fixes, and verification.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I automatically find and fix bugs in a web application?▼

Automated QA testing systematically identifies defects in a web application and iteratively fixes them in source code. It commits each fix atomically and re-verifies the application to ensure bugs are resolved.

What is a ship-readiness narrative in software verification?▼

A ship-readiness narrative summarizes QA outcomes using before and after health scores with fix evidence. It confirms whether a feature branch is ready for production release after automated testing and bug fixing.

Can I run tiered QA workflows on a feature branch?▼

Yes, tiered QA workflows support Quick, Standard, and Exhaustive testing tiers directly on feature branches. Each tier generates health scores, fix evidence, and a ship-readiness summary to validate code quality.

How do I verify bug fixes without manual testing?▼

Automated verification loops confirm bug fixes by re-testing the web application after each atomic source code commit. This deterministic execution process produces a verifiable report of outcomes without manual intervention.

What is the best way to test if a feature works before shipping?▼

Running structured QA tests on the feature branch is the best way to confirm readiness. This process identifies defects, applies atomic commits for fixes, and generates a ship-readiness summary with health scores.

When should I use an exhaustive QA workflow instead of a quick test?▼

Use the Exhaustive QA tier for deep verification of critical features, and the Quick tier for fast checks. Both produce health scores and fix evidence, but exhaustive testing provides a more comprehensive ship-readiness narrative.