qa-only

Run report-only QA tests that generate a structured report with health score, screenshots, and repro steps.

2|2|Updated Dec 1, 2024
One-click install
npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill qa-only-yaugourt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/Yaugourt/LiquidTerminal_Back/tree/main/.agents/skills/gstack/qa-only
Command: npx skills add https://github.com/Yaugourt/LiquidTerminal_Back --skill qa-only-yaugourt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing of a web app that produces a structured report with a health score, screenshots, and repro steps, but never applies fixes.

Core Features & Use Cases

  • Automated, report-only QA tests that generate a comprehensive report with evidence.
  • Use cases include "just report bugs" or "qa report only"; for full test-fix-verify, use /qa.
  • Proactively suggest improvements only when asked.

Quick Start

Run the QA-only skill on your app to generate a structured QA report without applying any fixes.

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 QA report with screenshots and repro steps for a web application?

To generate a QA report with screenshots and repro steps, run repeatable tests against your web application. The report-only testing process outputs a structured health score, evidence screenshots, and clear reproduction steps without applying any code fixes.

What is report-only QA testing and when should I use it?

Report-only QA testing identifies application issues and generates a structured report with a health score and evidence. Use this approach for on-demand workflows like bug reports when you need documentation without automatically applying code changes.

Can I use this QA testing approach to automatically fix bugs it finds?

No, this report-only QA testing approach never applies code changes or fixes. It strictly limits actions to supported tools like Bash, Read, Write, and WebSearch to generate evidence reports, leaving the actual bug fixing to a separate workflow.

What is the best way to document web application bugs with reproducible steps?

The best way to document web application bugs is using a report-only QA testing workflow. It automatically captures evidence screenshots, calculates a health score, and writes clear repro steps into a structured report for easy bug tracking.

What actions are limited during automated web application QA reporting?

Automated QA reporting limits actions to supported tools including Bash, Read, Write, AskUserQuestion, and WebSearch. It respects safety and scope boundaries by strictly prohibiting the application of any code changes during the testing process.