qa-only

Run report-only QA tests on web applications and generate structured health reports.

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

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.

Core Features & Use Cases

  • Automated, repeatable QA tests that mimic real user interactions.
  • Structured reports with health score, screenshots, and reproducible steps; no code changes are made.
  • Use Case: when you need an objective bug report without touching production code; for full verification, run /qa.

Quick Start

Run /qa to start a report-only QA pass on your web app.

Frequently Asked Questions about qa-only

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

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

Report-only QA testing systematically navigates and interacts with your web app to generate structured health reports, screenshots, and repro steps without applying any code changes.

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

Report-only QA testing strictly observes and documents potential issues with health scores and evidence, whereas a full test-fix-verify loop actively applies and verifies code changes to resolve the discovered bugs.

How do I generate a bug report with reproducible steps and screenshots for a web application?

You can generate a structured bug report with reproducible steps and screenshots by running an automated browser interaction tool that captures evidence and calculates a health score without touching production code.

Does report-only QA testing perform form interactions and basic checks on web apps?

Yes, report-only QA testing uses browser automation to perform form interactions and basic checks, observing results to document potential issues and write a detailed QA report with evidence.

When should I use a report-only QA testing approach instead of an automated fix?

Use a report-only QA testing approach when you need an objective bug report with health scores and repro steps for a web app but must avoid touching or modifying the production code base.