qa

Test web applications, fix defects, and commit atomic fixes.

10|3|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/olaafrossi/FoamPilot --skill qa-olaafrossi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/olaafrossi/FoamPilot/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/olaafrossi/FoamPilot --skill qa-olaafrossi

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". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary.

Core Features & Use Cases

  • Thorough manual and automated testing that mirrors real user flows across browsers and devices.
  • Bug reproduction, evidence gathering, and atomic fixes with re-verification.
  • Use Case: When a feature ships with a bug, run a QA cycle to reproduce, fix, verify, and ship.

Quick Start

Run a full QA cycle on the target URL, identify defects, and commit atomic fixes.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run end-to-end QA testing and automatically fix bugs in a web app?

End-to-end QA testing systematically tests web app user flows, locates defects, captures evidence, commits atomic source code fixes, and re-verifies each repair iteratively until the application passes.

What's the best way to find and fix bugs before a web app release?

Run a QA cycle before release to reproduce bugs, gather evidence, apply atomic fixes, and generate before/after health scores with a ship-readiness summary validating the web app across browsers and devices.

Can I run a quick QA test that only covers critical and high-severity bugs?

Yes, the Quick tier tests only critical and high-severity bugs, while the Standard tier adds medium severity and the Exhaustive tier includes cosmetic defects for comprehensive web app coverage.

Does automated QA testing work for regression checking across browsers and devices?

Automated QA testing mirrors real user flows across browsers and devices, supporting iterative regression checking by reproducing bugs, applying atomic fixes, and re-verifying fixes for repeatable test cycles.

How does a QA workflow verify that a bug fix actually resolves the issue?

The QA workflow commits each bug fix atomically and immediately re-verifies the repair by running test cycles again, producing before/after health scores and fix evidence confirming the resolution.

When do I need to run an exhaustive QA test cycle instead of a standard one?

Run an exhaustive QA test cycle when preparing for a major release that requires cosmetic-level defect validation, whereas standard cycles cover medium severity and quick cycles handle only critical issues.