qa

Run tiered QA testing and bug-fix cycles for web applications.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/antriksh-29/reddit-automation --skill qa-antriksh-29
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/antriksh-29/reddit-automation/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/antriksh-29/reddit-automation --skill qa-antriksh-29

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.

## Core Features & Use Cases

  • Manual-trigger QA: start a QA cycle and coordinate testing, fixes, and verification.
  • Tiered coverage: Quick, Standard, Exhaustive, with health scores and ship-readiness reports.
  • Evidence and context: Generates test evidence (screenshots, logs) and a structured report.

### Quick Start Type /qa to start a QA cycle and guide the system to test and verify the web app.

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 a web application?

Automated testing and bug fixing for a web application is handled by running structured QA cycles that test features, iteratively fix source code bugs, and commit fixes atomically while re-verifying results.

What is the best way to run QA tests and fix bugs before shipping a web app?

The best way to QA test and fix bugs is running tiered test cycles that execute deterministic scripts, capture screenshot evidence, generate health scores, and produce a final ship-readiness summary.

How does a tiered QA testing process work for finding bugs?

Tiered QA testing works by executing deterministic test scripts across three coverage levels: Quick for critical bugs, Standard for medium issues, and Exhaustive for cosmetic defects, yielding before and after health scores.

Do I need to provide a target URL to start testing my web app?

Yes, you need to supply a target URL or environment to start testing your web app, and you must commit atomic fixes to the source code during the bug-fixing process.

Can I generate a QA report with screenshots without automatically fixing the bugs?

Yes, you can generate a QA report with screenshots without fixing bugs by using a report-only mode, which produces test evidence and structured logs without committing source code changes.

What are the limitations of using automated QA cycles for web app testing?

A limitation of automated QA cycles is that they require manual triggering and user-supplied target URLs, meaning they do not passively monitor web apps or fix bugs without explicit atomic commits during the process.