qa

Test web applications, fix bugs, and verify fixes across three tiers.

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

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

  • QA testing workflow: systematic end-to-end testing across tiers (Quick, Standard, Exhaustive)
  • Automated evidence & ship-readiness: health scores, before/after comparisons, and a summary
  • Proactive guidance: alerts about potential work and validation needs

Quick Start

Run a QA pass on the current web app, fix every defect found, commit each fix atomically, and re-run tests to confirm ship-ready.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate regression testing and bug fixing for a web app?▼

Automated regression testing for a web app runs systematic QA passes, identifies bugs, iteratively fixes them in source code, commits each fix atomically, and re-verifies to confirm ship-readiness.

What is the best way to run a bug hunt on my web application before release?▼

The best way to run a bug hunt on a web application is using an exhaustive QA tier that tests critical, high, medium, and cosmetic defects, producing before and after health scores and a ship-readiness summary.

How does systematic QA testing generate fix evidence and health scores?▼

Systematic QA testing generates fix evidence and health scores by relying on automated test harnesses and reproducible environments to execute end-to-end tests and validate that source code fixes resolve identified bugs.

Can I generate a QA test report without automatically modifying my source code?▼

Yes, you can generate a QA test report without modifying source code by using a report-only mode, which runs the testing workflow and identifies bugs without committing atomic fixes.

What testing tiers should I use for feature verification in a web application?▼

For feature verification in a web application, you can use Quick, Standard, or Exhaustive testing tiers, which progressively cover critical, high, medium, and cosmetic defects to validate readiness.

Do I need a reproducible environment to run automated QA tests?▼

Yes, you need a reproducible environment to run automated QA tests, because the testing workflow relies on automated test harnesses within these environments to accurately produce health scores and fix evidence.