qa

Test web applications as a real user and fix discovered bugs.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/GenEducation/GenedUIProject --skill qa-geneducation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/GenEducation/GenedUIProject/tree/main/.gemini/skills/qa
Command: npx skills add https://github.com/GenEducation/GenedUIProject --skill qa-geneducation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill finds broken behavior in a web application, then fixes the source code and rechecks the result so the app is ready to ship.

Core Features & Use Cases

  • Real-user QA: Click through pages, forms, navigation, states, and responsive layouts the way a customer would.
  • Test then fix: When bugs appear, apply atomic source-code fixes and verify each change before moving on.
  • Evidence-based reporting: Produce before-and-after proof, issue severity, and ship-readiness summaries so teams know what changed.
  • Use Case: You just finished a feature and want to know whether it actually works, including edge cases, console errors, and visual regressions.

Quick Start

Use the qa skill to test this site, fix any bugs you find, and return a verified report with before-and-after evidence.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I find and fix bugs in a web application before shipping?▼

To find and fix bugs in a web application, you can run a real-user QA process that clicks through pages, forms, and navigation, applies atomic source-code fixes, and verifies each change with before-and-after evidence for ship readiness.

What is regression testing and how does it verify code changes?▼

Regression testing checks diff-scoped changes in a web application by executing real-user interactions, verifying that recent code commits have not introduced new console errors or broken existing states, navigation, or responsive layouts.

How do I test web app accessibility and responsive layouts like a real user?▼

Testing web app accessibility and responsive layouts involves clicking through site states and forms the way a customer would, identifying accessibility gaps and visual regressions, and applying atomic fixes to resolve them.

Can I automate bug fixing and get a ship-readiness report for my web app?▼

Yes, you can automate bug fixing by testing web application behavior, applying atomic source-code fixes, and generating an evidence-based report with issue severity tiers and before-and-after proof to confirm ship readiness.

What's the best way to hunt down broken links and console errors across my site?▼

The best way to hunt down broken links and console errors is to run a site-wide QA test that clicks through pages and navigation like a real user, logs issues by severity, and verifies atomic fixes with before-and-after evidence.

Does this QA testing approach work for edge cases and visual regressions in forms?▼

Yes, this QA testing approach works for edge cases and visual regressions in forms by executing real-user interactions across various states and responsive layouts, identifying broken behavior, and verifying atomic source-code fixes.