qa-only

Test a web application and produce a structured QA report with evidence and repro steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing often focuses on fixing bugs, but sometimes you just need a thorough, evidence-backed report that identifies issues without changing the code or deployment. This Skill enables that capability by running tests, capturing evidence, and compiling a structured report.

Core Features & Use Cases

  • 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.

Quick Start

Instruct the agent to run a report-only QA pass against the target app without making code changes.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I run a web application QA test that only reports bugs without fixing code?

Report-only QA testing identifies bugs in a web application without applying fixes, producing a structured QA report with evidence, screenshots, and repro steps. You instruct the agent to run a report-only pass and it will never change your code or deployment.

What is the best way to generate a bug report with repro steps and screenshots for a web app?

A bug report-only QA workflow systematically tests a web application to compile evidence-backed reports. It captures screenshots and details repro steps, assembling a structured report with a health score so you can document issues without altering the application.

Does report-only QA testing modify my web application code during validation?

Report-only QA testing does not modify your code. It is designed for validation without code changes, meaning the agent will only run tests, gather evidence, and assemble a report rather than attempting to fix identified bugs.

Can I use this report-only QA workflow if I later need to test, fix, and verify the bugs?

For a full test-fix-verify loop, you should use a complete QA workflow rather than the report-only approach. The report-only skill is ideal when asked to just report bugs, but it lacks the capability to apply fixes and re-run validation.

What do I need to set up to orchestrate tests and gather evidence for a bug report?

To orchestrate tests, gather evidence, and assemble the report, the environment requires Bash, Read, Write, AskUserQuestion, and WebSearch capabilities. These tools allow the agent to interact with the web app and capture necessary screenshots and repro steps.