qa-only

Run structured QA tests on web applications and produce health reports with screenshots and repro steps.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/him55710-sudo/uni-foli --skill qa-only-him55710-sudo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/him55710-sudo/uni-foli/tree/main/.agents/skills/gstack-qa-only
Command: npx skills add https://github.com/him55710-sudo/uni-foli --skill qa-only-him55710-sudo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing that systematically examines a web application and produces a structured report with a health score, screenshots, and reproduction steps — but never fixes anything.

Core Features & Use Cases

  • Structured QA reports with health scores, screenshots, and reproducible steps.
  • Guidance for when to request a pure bug report or a full QA pass.
  • Proactively suggest reporting improvements or bug details when the user asks for a report without code changes.

Quick Start

Run a report-only QA pass against your app to generate a structured health report with screenshots 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 run a report-only QA pass on a web application?

A report-only QA pass systematically examines a web application to identify bugs and regressions, producing a structured report with health scores, screenshots, and reproduction steps without applying any fixes.

What is included in a structured QA health score report?

A structured QA health score report includes a quantified health score, visual screenshots of identified issues, and step-by-step reproduction notes for bugs and regressions found in the application.

Can I get pure bug reports without code changes for my single-page app?

Yes, you can request a pure bug report for single-page apps and multi-page sites that proactively suggests reporting improvements and bug details without modifying your codebase.

Does this QA testing approach fix bugs automatically during the test run?

No, this QA testing approach is strictly report-only and never fixes anything, ensuring a non-fixing automated run that solely identifies bugs and generates a formal report.

When should I request a full QA cycle instead of a pure bug report?

You should request a full QA cycle when you need comprehensive structured testing guidance across your application, whereas a pure bug report focuses solely on documenting the identified issues and regressions.