qa

Test web applications, reproduce issues, and commit atomic fixes.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/mgher668/surf-ai --skill qa-mgher668
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/mgher668/surf-ai/tree/main/.agents/skills/gstack/qa
Command: npx skills add https://github.com/mgher668/surf-ai --skill qa-mgher668

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA testing and bug-fix cycles for web applications, reducing cycle time by automating discovery, reproduction, and verification of issues.

Core Features & Use Cases

  • End-to-end QA exploration across pages and components.
  • Atomic fixes with re-verification and health-score reporting.
  • Generates before/after evidence and ship-readiness summaries for release readiness.

Quick Start

Initiate the QA workflow on your project, reproduce a reported issue, apply a small atomic fix, and re-run verification.

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 fixing for a web application?

Automate web application QA testing by running end-to-end exploration across pages and components, applying atomic bug fixes, and re-verifying issues. This workflow reduces cycle time by automating discovery, reproduction, and verification while generating evidence like screenshots and health scores.

How do I generate QA reports and evidence for release readiness?

Generate QA reports by executing test plans and capturing before and after evidence including screenshots and health scores. This produces ship-readiness summaries that verify regression issues are resolved and document the application's health state for release.

What do I need to provide to start a regression verification workflow?

You need to provide a test plan and an accessible URL to start regression verification. The workflow requires the ability to commit fixes atomically while it produces QA reports, screenshots, and a health score based on the provided inputs.

Can I adjust the depth of end-to-end QA exploration for my web application?

You can adjust the depth of QA exploration using tiered focus options including Quick, Standard, and Exhaustive. This allows you to balance testing thoroughness against cycle time depending on your specific regression verification and issue reproduction needs.

What is the best way to reproduce a reported issue and verify the fix?

The best way to reproduce a reported issue is to initiate a QA workflow on your project, apply a small atomic fix, and re-run verification. This ensures the bug fix is validated through before and after health reporting and evidence generation.