qa-only

Automate report-only QA testing for web applications with health scoring and screenshots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically tests web applications to surface bugs without applying fixes, producing a structured health report with evidence.

Core Features & Use Cases

  • Systematic bug reporting without fixes
  • Health scoring and repro steps
  • Visual evidence through screenshots and reports

Quick Start

Run the /qa command on your project to generate a structured bug report with health score and repro steps.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I automate QA testing to find bugs without applying code fixes?

Report-only QA testing automates web application scans to surface bugs without applying fixes, producing a structured health report with evidence. It operates across entire apps or focused pages to trigger repro-steps collection and health scoring.

How do I generate a bug report with reproduction steps for my web app?

Generating a bug report with repro steps involves running an automated QA command on your project. The system captures screenshots, calculates a health score, and outputs a structured report to the local .gstack/qa-reports directory.

Can I run automated QA testing across specific pages instead of a full web application?

Automated QA testing supports both entire web applications and focused pages. You can target specific areas to collect reproduction steps, capture screenshots, and generate a structured health report without modifying your underlying codebase.

What is a health score in automated web app bug reporting?

A health score in automated bug reporting quantifies the overall stability of a web application based on surfaced defects. It is generated alongside reproduction steps and screenshot evidence to provide a structured summary of application quality.

Where are automated QA testing reports and screenshots stored?

Automated QA reports and screenshots are stored in the .gstack/qa-reports directory within your local environment. The QA framework orchestrates the output generation when responding to testing prompts.

Does report-only QA testing modify my source code when finding bugs?

Report-only QA testing does not modify source code. It systematically surfaces bugs and generates visual evidence with reproduction steps while leaving the application fixes entirely separate from the testing process.