qa

Run tiered QA testing on web applications and fix detected bugs.

1|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/tblakex01/conductor-playground --skill qa-tblakex01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/tblakex01/conductor-playground/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/tblakex01/conductor-playground --skill qa-tblakex01

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. For report-only mode, use /qa-only. (gstack) Voice triggers (speech-to-text aliases): "quality check", "test the app", "run QA". allowed-tools:

  • Bash
  • Read
  • Write
  • Edit
  • Glob
  • Grep
  • AskUserQuestion
  • WebSearch triggers:
  • qa test this
  • find bugs on site
  • test the site

Core Features & Use Cases

  • Tiered QA strategies: Quick, Standard, and Exhaustive assessments with health-score reporting.
  • Iterative bug fixing: commit each fix atomically and re-verify to ensure regression-free changes.
  • Ship-readiness reporting: generate before/after health scores, fix evidence, and a ship-readiness summary.

Quick Start

Run the QA skill against your target web application to start automated testing, fix detected issues, and re-run verification after each fix.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate testing and bug fixing for my web application?

Automated QA testing runs scripted checks on a web application to find defects, iteratively fix source code, and verify changes. It commits fixes atomically to ensure regression-free updates.

What is the best way to run a quick quality check before shipping a site?

A Quick QA tier targets critical and high-severity defects to balance speed and depth. It generates before and after health scores and a ship-readiness summary for rapid deployment validation.

How does tiered QA testing balance speed and depth across projects?

Tiered QA testing offers Quick, Standard, and Exhaustive levels. Quick assesses critical issues, Standard adds medium severity, and Exhaustive covers cosmetic defects, scaling testing depth against time constraints.

Can I generate a QA report without automatically modifying the source code?

Yes, you can generate a report-only health assessment without modifying source code. The report-only mode performs scripted checks and outputs structured health scores and defect lists without applying fixes.

What is included in the ship-readiness summary after a QA cycle?

The ship-readiness summary includes before and after health scores, fix evidence, and structured defect reports. It confirms resolved issues through atomic code commits and re-verification.

When should I use exhaustive testing instead of standard QA checks?

Use exhaustive testing to verify cosmetic defects alongside critical, high, and medium severity issues. Standard QA covers up to medium severity, while exhaustive mode ensures complete visual and functional ship-readiness.