qa-only

Identify and report QA findings for web applications without code changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you perform QA testing on a web app and produce a structured report with health score, screenshots, and repro steps, without making any code changes.

Core Features & Use Cases

  • Automated, report-only QA runs that validate UI, flows, and performance without applying fixes.
  • Produces a structured QA report with health score, annotated screenshots, and reproducible steps.
  • Guides users on when to use /qa vs /qa-only and supports interactive prompts for how to proceed.

Quick Start

Run a QA session on your live app by starting a /qa-only workflow to generate a detailed health report without applying fixes.

Frequently Asked Questions about qa-only

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run QA testing on a web app without changing the code?

Read-only QA testing evaluates your live web app or feature branch without applying code changes. It uses predefined tools and guided prompts to validate UI and flows safely, ensuring your application remains unmodified while identifying issues.

How do I generate a QA report with repro steps and screenshots for a web application?

Automated QA testing workflows produce a structured report containing a health score, full screenshots, and reproducible steps. By running a report-only session on your web application, you get evidence-rich documentation of UI and flow validations.

What is a health score in web application QA reporting?

A health score in QA reporting is a quantitative metric evaluating your web application's overall quality. Generated through end-to-end test orchestration, it summarizes UI, flow, and performance validation results into a structured score within the final report.

When should I use a report-only QA workflow instead of automated fixing?

Use a report-only QA workflow when you need formal evidence-rich reporting with screenshots and repro steps on a live app, but want to avoid automated code changes. It safely evaluates feature branches and generates a health-score report before any fixes are applied.

Can I test feature branches and live apps using a read-only QA process?

Yes, read-only QA testing applies to both live web apps and feature branches. It performs end-to-end test orchestration safely, validating UI and flows without modifying the codebase, making it ideal for assessing deployment readiness across environments.