qa

Run automated web application QA tests and fix discovered bugs iteratively.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual QA testing is slow, inconsistent, and often misses critical bugs before shipping. This Skill eliminates the gap between testing and fixing by automatically running QA tests, identifying issues, and iteratively fixing them in the source code.

Core Features & Use Cases

  • Automated QA Testing: Runs comprehensive tests across visual, functional, UX, performance, and accessibility dimensions.
  • Iterative Bug Fixing: Automatically fixes discovered bugs, commits each fix atomically, and re-verifies the fix works.
  • Tiered Coverage: Choose Quick (critical/high only), Standard (+ medium), or Exhaustive (+ cosmetic) based on your release needs.
  • Health Scoring: Produces before/after health scores and ship-readiness summaries to inform go/no-go decisions.
  • Use Case: When you're about to ship a feature and want to catch regressions, or when a stakeholder reports "this is broken" and you need to systematically find and fix the issue.

Quick Start

Use the qa skill to test the current web application, automatically fix any bugs found, and generate a ship-readiness report with health scores.

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 web applications before shipping?

Automated QA testing systematically validates visual, functional, UX, performance, and accessibility dimensions across web applications, then iteratively fixes discovered bugs in source code with atomic commits and re-verifies each fix to ensure ship-readiness.

What is tiered coverage in QA testing and when do I need it?

Tiered QA coverage lets you choose validation depth: Quick targets critical and high severity issues, Standard adds medium severity, and Exhaustive includes cosmetic issues, matching validation depth to your specific release needs.

How do I get a ship-readiness summary with health scores for my web application?

Ship-readiness summaries with health scores are produced by running automated QA tests that calculate before and after health metrics, directly informing go or no-go release decisions for your web application.

Can I use browser automation to triage and fix reported bugs in source code?

Browser automation combined with source code editing tools can systematically triage reported bugs by testing the web application, identifying the issue, applying an atomic source code fix, and re-verifying that the fix works.

Does automated QA testing work for pre-release validation of web applications?

Automated QA testing works effectively for pre-release validation of web applications by running comprehensive regression tests across multiple dimensions and producing ship-readiness summaries to validate release quality.