qa-only

Test a web application and generate a QA report with health score and screenshots.

Updated Jun 16, 2026

Search Tags:#qa #report generation #bug reporting #health score #web application testing

Ready to run

npx skills add https://github.com/miko06/MedicineSimulator --skill qa-only-miko06

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/miko06/MedicineSimulator/tree/main/.opencode/skills/gstack-qa-only
Command: npx skills add https://github.com/miko06/MedicineSimulator --skill qa-only-miko06

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill systematically tests a web application and produces a structured report with a health score, screenshots, and repro steps, without making any fixes. It is designed for situations where only a QA report is required.

Core Features & Use Cases

Systematic Web Application Testing: Tests web applications and generates a comprehensive report.
Health Score and Screenshots: Provides a health score and screenshots to visualize the test results.
Use Case: When asked to "just report bugs" or "qa report only", this Skill can be used to generate a detailed QA report without making any changes to the application.

Quick Start

Invoke the qa-only skill for a report-only QA test of your web application.

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 for a web application without modifying any code?▼

To generate a QA report without modifying code, you can use a report-only testing approach that systematically evaluates your web application and outputs a structured health score, screenshots, and repro steps while leaving the application unchanged.

Can I get a health score and screenshots from web application testing?▼

Yes, web application testing can produce a health score and screenshots alongside structured repro steps, giving you a comprehensive visual and metric-based report of the application's current state.

What is the best way to run report-only bug reporting on a web app?▼

The best way to run report-only bug reporting is to invoke a QA testing process that systematically identifies issues and documents them with repro steps and screenshots, intentionally skipping any code fixes or application changes.

Does report-only QA testing include steps to reproduce the bugs it finds?▼

Yes, report-only QA testing includes repro steps for identified bugs, ensuring your development team has the exact instructions needed to replicate and address the issues found during the systematic web application test.

When should I use a report-only QA test instead of automated bug fixing?▼

You should use a report-only QA test when you need a detailed assessment of your web application's health score and issues but want to strictly prohibit any automatic fixes or modifications to the application codebase.