qa-only

Run report-only QA testing on web applications and generate health scores, screenshots, and repro steps.

1|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/zhu637882-stack/jiaoyi --skill qa-only-zhu637882-stack
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/zhu637882-stack/jiaoyi/tree/main/qoder-config-backup/skills/gstack-qa-only
Command: npx skills add https://github.com/zhu637882-stack/jiaoyi --skill qa-only-zhu637882-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".

Core Features & Use Cases

  • Structured QA reports with a health score, screenshots, and reproducible steps for web apps.
  • Operates in a read-only mode: does not modify code or deployments; ideal when a user asks for a "qa report only" workflow.
  • Voice and text triggers to initiate quick, non-intrusive QA narration.

Quick Start

Run the qa-only skill to generate a bug report for the current web application 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 bug report for a web app without changing the code?

A report-only QA workflow tests your web application systematically to produce a structured health score, screenshots, and reproducible steps without applying any code fixes. It is triggered by requests like 'qa report only' or 'test but don't fix'.

What is included in a structured QA health score report?

A structured QA health score report includes a quantified health score, screenshots of identified issues, and detailed reproducible steps. It provides a thorough bug narrative for web applications while operating in a strict read-only mode.

Can I run QA testing on a web app using Bash without applying fixes?

Yes, you can run deterministic QA testing using allowed tools like Bash, Read, Write, WebSearch, and AskUserQuestion without applying fixes. This approach loads contextual artifacts for reproducibility and analysis while maintaining a strict read-only mode.

Does report-only QA testing write repro steps for bugs it finds?

Yes, report-only QA testing explicitly writes detailed reproducible steps for discovered bugs. It systematically analyzes the web application and documents the findings in a structured report complete with health scores and screenshots.

What is the difference between a full test-fix-verify loop and report-only QA?

Report-only QA strictly produces a structured bug report with health scores and screenshots without touching code. A full test-fix-verify loop goes further by actually modifying the codebase to resolve the discovered issues and verifying the applied fixes.

When should I use a non-intrusive QA report instead of fixing bugs directly?

Use a non-intrusive QA report when you need to identify bugs, generate screenshots, and document repro steps without altering deployments. It is ideal for assessing web application health and producing a thorough bug narrative before committing to fixes.