qa

Run tiered QA tests, fix bugs atomically, and report ship-readiness for web apps.

Updated Feb 27, 2026
One-click install
npx skills add https://github.com/curielmc/beat-SPY --skill qa-curielmc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/curielmc/beat-SPY/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/curielmc/beat-SPY --skill qa-curielmc

SYSTEM DOCUMENTATION & REQUIREMENTS

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

  • Automated QA workflow: run tests, fix bugs atomically, re-verify, and report ship-readiness
  • Tiered testing: Quick, Standard, Exhaustive with progressive depth
  • Evidence & health: before/after scores, fix evidence, and ship-readiness summaries
  • Use cases: when asked to QA a site, verify feature readiness, or perform regression testing

Quick Start

Tell me the target URL and scope, and I will start a QA run, fix cycles, and verification.

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 my web app?

Automated QA testing executes test cycles, iteratively fixes source code bugs atomically, and re-verifies the web app. You provide a target URL and scope, and the workflow runs bug reproduction, fixes, and ship-readiness verification.

What is the best way to verify web app ship-readiness before release?

Ship-readiness verification generates before and after health scores alongside fix evidence. It evaluates interactive web applications through tiered testing to determine if critical, medium, or cosmetic bugs are resolved for deployment.

Does automated bug fixing support atomic commits for regression testing?

Automated bug fixing supports atomic commits by isolating each source code change during the QA cycle. This ensures every bug fix is individually verifiable during re-verification, preventing regression issues across the web app.

Can I choose how deep the QA testing goes for my web application?

Tiered QA testing allows you to choose Quick for critical and high bugs only, Standard to include medium bugs, or Exhaustive to cover cosmetic issues. This scopes the bug reproduction and fixing cycles to your project needs.

What tools do I need to automate web app QA and bug fixing cycles?

Automating QA and bug fixing cycles requires tool support including Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion, and WebSearch. These tools enable the workflow to test, patch source code, and verify fixes autonomously.

Why are health scores needed when testing a site for bugs?

Health scores provide before and after metrics to quantify bug fixing progress during QA cycles. They serve as evidence of ship-readiness by showing the measurable impact of atomic commits and bug re-verification on the web app.