qa-only

Tests web applications and generates structured bug reports with health scores and screenshots.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill qa-only-raghavbadhwar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/raghavbadhwar/rstack/tree/main/qa-only
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill qa-only-raghavbadhwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often need an objective assessment of a web application's quality without immediately changing code. This Skill systematically tests a web application and produces a structured report with a health score, screenshots, and reproduction steps, while never modifying any source files. ## Core Features & Use Cases - Report-only QA testing: Systematically exercises a web application and documents every bug found, with zero code changes. - Structured output: Produces a report containing a health score, annotated screenshots, and step-by-step reproduction instructions for each issue. - Use Case: Before a release, ask for a read-only QA pass on your staging site. You receive a prioritized bug report with screenshots and repro steps that engineers can triage, while the codebase stays untouched. ## Quick Start Ask the agent to run a report-only QA pass on your web app and list every bug found with screenshots and repro steps, without fixing anything.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I get a bug report without the AI changing my code?

Invoke the qa-only skill, which tests the web application and writes a structured report but never edits source files. It is explicitly designed for report-only workflows, unlike the full /qa skill which runs a test-fix-verify loop.

What does the QA report include?

The report contains an overall health score, screenshots of the tested pages and failures, and step-by-step reproduction instructions for each bug found. This gives engineers everything needed to triage and fix issues independently.

What is the difference between qa-only and the full qa skill?

qa-only stops at reporting: it tests and documents bugs but never fixes them. The full /qa skill runs a complete test-fix-verify loop that modifies code and re-tests until issues are resolved.

When should I use report-only QA testing?

Use it before releases, when auditing someone else's code, or when you want an independent quality assessment before deciding what to fix. It is ideal when code changes require separate review or approval.

Can qa-only run in headless or CI environments?

Yes. The skill detects headless sessions in its preamble and adjusts behavior, blocking on interactive prompts rather than waiting for input that cannot arrive. Spawned sessions auto-choose recommended options and report results as prose.