qa-only

Generate a structured browser QA report with screenshots and console errors.

8|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/MFS-code/gstack --skill qa-only-mfs-code
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/MFS-code/gstack/tree/main/qa-only
Command: npx skills add https://github.com/MFS-code/gstack --skill qa-only-mfs-code

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you verify a web app still works by running a realistic, browser-based QA pass and producing a structured report with evidence, without applying any fixes.

Core Features & Use Cases

  • Manual-trigger QA reporting only: Runs only when you explicitly ask for it with /qa-only, ensuring it never attempts to fix issues.
  • Systematic web app testing with evidence: Produces a structured output including a health score, screenshots, and clear repro steps so you can reproduce problems quickly.
  • Best for “just report bugs” moments: Use it when someone asks for a QA bug report, a regression snapshot for stakeholders, or a test summary before engineering changes.

Quick Start

Use the qa-only skill to test a target site and generate a bug report by asking: /qa-only and include the URL of the app you want tested.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I generate a browser QA report for a web app without modifying any code?

To generate a browser QA report without code changes, you trigger a testing pass that navigates your web app, captures screenshots, and logs console errors. This produces a structured health score report with clear bug reproduction steps.

Can I run regression testing on web forms and interactive flows using browser automation?

Yes, you can run regression testing across pages, forms, and interactive flows using browser automation. The process captures screenshots and console errors to produce a structured report without altering your application's UI or backend code.

How does a health score QA report work for web applications?

A health score QA report works by systematically navigating a web application to evaluate its current state. It aggregates captured screenshots and console errors into a quantifiable score, providing a clear snapshot of app stability before engineering changes.

Does browser QA testing support authenticated pages requiring user credentials or cookies?

Browser QA testing supports authenticated pages through optional auth handling via user-provided credentials or cookies. This allows the automation to navigate past login screens and test restricted interactive flows within the web application.

What is the best way to report app bugs with screenshots and console errors for stakeholders?

The best way to report app bugs for stakeholders is generating a structured QA report that includes a health score, screenshots, and console errors. This provides reproducible evidence of issues without applying any fixes to the codebase.

What are the limitations of using a manual-trigger QA reporting skill for web apps?

The limitation of a manual-trigger QA reporting skill is that it only runs when explicitly invoked and never attempts to fix identified issues. It requires building a specific browse binary and is strictly for generating bug reports, not automated code remediation.