qa

Run tiered web app QA testing and iteratively fix bugs with atomic commits.

48|2|Updated Dec 23, 2017
One-click install
npx skills add https://github.com/g4rcez/dotfiles --skill qa-g4rcez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/g4rcez/dotfiles/tree/main/.ai/skills/qa
Command: npx skills add https://github.com/g4rcez/dotfiles --skill qa-g4rcez

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

  • End-to-end QA that identifies regressions, creates atomic fixes, and re-verifies changes.
  • Tiered testing approaches (Quick, Standard, Exhaustive) with health-score reporting and ship-readiness summaries.
  • Generates reproducible steps, evidence, and reports to communicate outcomes.

Quick Start

Run the QA workflow on your project to start automated testing, bug reproduction, and fix verification.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate web app QA testing and bug fixing in one workflow?

Automated QA testing and iterative bug fixing run in a single workflow by rigorously testing the web app, applying atomic source code repairs, and re-verifying each fix. It produces before/after health scores and a ship-readiness summary.

What's the best way to find bugs in a web application and generate reproduction steps?

To find bugs in a web application, run an automated QA test tier to identify regressions and generate reproducible steps with evidence. This process triages issues across critical, high, medium, and cosmetic severity levels.

Can I run QA tests on my web app without automatically committing bug fixes?

Yes, you can run report-only QA tests on your web app without committing fixes by using report-only mode. This mode performs testing and generates health scores and evidence without applying atomic commits during repairs.

Does tiered web app testing support different levels of bug triage?

Tiered web app testing supports different levels of bug triage through Quick, Standard, and Exhaustive modes. Quick covers critical and high issues, Standard adds medium, and Exhaustive includes cosmetic bugs for comprehensive verification.

How does automated bug fixing verify changes before shipping a web app?

Automated bug fixing verifies changes by committing each repair atomically and re-running tests to confirm the fix. It generates before/after health scores and a ship-readiness summary to communicate deployment confidence.

What is atomic commit bug fixing and when do I need it for web app development?

Atomic commit bug fixing is the process of isolating each source code repair into a single, verifiable commit during web app development. You need it for disciplined change management when iteratively fixing bugs and verifying readiness.