qa-only

Run report-only QA tests and generate a structured health report with screenshots.

1|Updated May 6, 2026

Search Tags:#testing #screenshots #qa #bug report #health score #repro steps

Ready to run

npx skills add https://github.com/yckkkk/reo --skill qa-only-yckkkk

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/yckkkk/reo/tree/main/.agents/skills/qa-only
Command: npx skills add https://github.com/yckkkk/reo --skill qa-only-yckkkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill runs tests to surface issues in a web application without applying any code changes, delivering a structured bug report with a health score, screenshots, and reproducible steps.

Core Features & Use Cases

Systematic bug discovery and health reporting without automatic fixes.
Generates a reproducible report including a health score, screenshots, and clear repro steps.
Use when asked to "just report bugs", "qa report only", or "test but don't fix"; can route to /qa for the full test-fix-verify loop.

Quick Start

Ask the qa-only skill to run a report on the current web app to generate a structured QA health report.

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 with reproducible steps without applying code fixes?▼

To generate a bug report with reproducible steps without applying fixes, use a report-only QA testing approach. It systematically surfaces web application issues and outputs a structured health report containing a health score, screenshots, and clear reproduction instructions.

What is a QA health score and how does it help with bug triage?▼

A QA health score is a metric generated during report-only testing to quantify the overall stability of a web application. It helps prioritize bug triage by summarizing discovered issues alongside screenshots and reproducible steps in a single structured report.

Can I run regression checks and exploratory testing without modifying my web application?▼

Yes, you can run regression checks and exploratory testing without modifying your web application using a report-only QA workflow. It systematically evaluates the application state to surface bugs and generates a health report, ensuring the codebase remains untouched.

How do I escalate a bug found during a report-only QA cycle to a full fix?▼

To escalate a bug found during a report-only QA cycle, route the structured report to the full test-fix-verify loop. This transitions the process from merely surfacing issues with reproducible steps to actively applying and verifying code fixes.

Does report-only QA testing work for pre-demo validations?▼

Yes, report-only QA testing works effectively for pre-demo validations. It systematically surfaces issues in the web application and generates a structured health report with screenshots, allowing you to verify stability and resolve critical bugs before a demonstration.