qa

Run QA tests on web applications and commit atomic bug fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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".

Core Features & Use Cases

  • Automated QA testing across web applications, including test execution, bug reproduction, and atomic commits of fixes.
  • Health-score reporting and ship-readiness assessment after each QA cycle.
  • Guided decision-making with prompts to route to next skills (qa, investigate, ship) based on findings.

Quick Start

Invoke the qa skill to start automated QA testing on your web application.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate QA testing and bug fixes for my web application?

Automated QA testing executes test cycles across your web application, iteratively fixes discovered bugs in source code, commits each fix atomically, and re-verifies the results to ensure stability.

Can I run a quick health check or regression test before committing changes?

Yes, you can run quick health checks and regression tests. The process supports commit-time verifications, applying before and after health scores to measure the impact of your source code changes.

How does automated bug fixing handle source code commits during testing?

Automated bug fixing reproduces discovered issues, applies patches to the source code, and commits each fix atomically. It then re-verifies the web application to confirm the bug is resolved without regressions.

Do I need to manually review ship-readiness after automated web app testing?

Automated web app testing generates ship-readiness summaries and evidence of fixes automatically. Guided gating prompts help route your next decisions, indicating whether to investigate further or proceed.

What is the best way to evaluate web application health scores after a bug fix?

Evaluating web application health scores involves comparing before and after metrics generated post-fix. The testing cycle provides these scores alongside ship-readiness summaries to validate iterative bug fixes improve stability.