qa-only

Name: qa-only
Availability: InStock
Author: Haohao

Produce report-only QA evidence with reproduction steps and screenshots.

779|80|Updated Jun 20, 2025

Search Tags:#testing #screenshots #qa #browser testing #report #reproduction steps #bug evidence

Ready to run

npx skills add https://github.com/Haohao-end/openagent --skill qa-only-haohao-end

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/Haohao-end/openagent/tree/main/api/internal/core/skills/catalog/qa-only
Command: npx skills add https://github.com/Haohao-end/openagent --skill qa-only-haohao-end

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams validate whether a page or workflow has issues by producing an organized QA report with clear evidence, without attempting to change or repair anything.

Core Features & Use Cases

Report-only QA testing: Collects potential problems and compiles results into a structured deliverable rather than applying fixes.
Evidence capture for reproducibility: Documents reproduction steps, screenshots, and impact scope to speed up investigation.
Exploratory QA support: Works well when the goal is discovery and assessment, such as exploratory browser-based testing.

Quick Start

Ask the AI to run a report-only QA pass on the target page and produce a structured issue report with reproduction steps, screenshots, and a problem checklist.

Frequently Asked Questions about qa-only

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

FAQPage Schema

What is report-only QA testing and when do I need it?▼

Report-only QA testing is an exploratory browser testing process that discovers UI or workflow defects and compiles a structured findings document. You need it when you want bug evidence and impact assessment without applying automated fixes or code changes.

How do I document reproduction steps for a suspected UI defect?▼

To document reproduction steps for a suspected UI defect, run an exploratory browser testing pass that records the exact actions taken, captures screenshots, and compiles a structured QA report detailing the problem checklist and affected scope.

Can I use this for exploratory browser testing without applying code fixes?▼

Yes, you can use this for exploratory browser testing because it follows a strict no-fix workflow. It validates pages, captures bug evidence like screenshots and reproduction steps, and outputs a structured QA report without attempting any remediation.

What is the best way to compile bug evidence for a structured QA report?▼

The best way to compile bug evidence for a structured QA report is to run a report-only QA pass that discovers problems, records reproduction steps, captures screenshots, and assesses the affected scope into a single deliverable for investigation.

Does browser testing for bug evidence require any specific testing frameworks?▼

Browser testing for bug evidence requires no specific testing frameworks or dependencies. It operates as a standalone exploratory testing session to validate pages and produce a structured findings document with reproduction steps and screenshots.

Why collect screenshots and reproduction steps instead of fixing bugs directly?▼

Collecting screenshots and reproduction steps instead of fixing bugs directly speeds up investigation by providing clear, structured bug evidence. This report-only approach assesses impact scope and documents defects without the risk of introducing automated remediation errors.