qa

Test web applications, fix bugs, and produce health scores.

Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Analog-Labs/pixelport-launchpad --skill qa-analog-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/Analog-Labs/pixelport-launchpad/tree/main/.agents/skills/gstack/qa
Command: npx skills add https://github.com/Analog-Labs/pixelport-launchpad --skill qa-analog-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I systematically test a web application and fix bugs automatically?

To systematically test a web application and fix bugs automatically, you need an iterative QA process that verifies features, applies source code fixes, and commits each fix atomically. This approach includes re-verifying changes and producing health scores.

Can I run QA testing on a web app without automatically committing bug fixes?

Yes, you can run QA testing on a web app without automatically committing bug fixes by using a report-only mode. This mode generates health scores and identifies issues without modifying the source code or creating atomic commits.

What is the best way to track ship-readiness after iterative bug fixes?

The best way to track ship-readiness after iterative bug fixes is to generate before and after health scores alongside a ship-readiness summary. This requires clear documentation of test plans and automated evidence for each verification tier.

Does automated QA testing support different levels of verification depth?

Automated QA testing supports different levels of verification depth through three tiers: Quick for critical and high severity issues, Standard for adding medium severity checks, and Exhaustive for including cosmetic verification across feature changes.

How do I reproduce and fix web app bugs found during testing?

To reproduce and fix web app bugs found during testing, the QA process iteratively fixes bugs in the source code and commits each fix atomically. It then re-verifies the application to ensure the bug fix is effective and produces fix evidence.

When do I need to use an exhaustive QA testing approach for my application?

You need to use an exhaustive QA testing approach when you require comprehensive verification across all feature changes, including cosmetic issues. This ensures maximum ship-readiness by producing detailed before and after health scores and comprehensive fix evidence.