qa-only

Automate browser-based QA testing and generate structured reports with evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often rely on manual, ad-hoc testing that produces incomplete bug reports and delays fixes. qa-only provides a repeatable, structured QA workflow that yields a comprehensive report with health scores, evidence, and reproducible steps, while explicitly avoiding any code changes.

Core Features & Use Cases

  • Systematic web app testing that generates a structured bug report with health score, screenshots, and repro steps — but never applies fixes.
  • Proactively suggests when a user wants a bug report without any code changes, enabling smooth handoff to engineering.
  • Use cases include exploratory QA, regression checks on feature branches, and pre-release verification.

Quick Start

Ask qa-only to run a full QA pass on your target URL.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I automate QA testing for a web app without applying code fixes?

To automate QA testing without fixes, you run a browser-based validation pass on the target URL. The process generates a structured report containing health scores, screenshots, and reproducible steps, explicitly avoiding any code modifications during the workflow.

What is a structured bug report with reproducible steps?

A structured bug report with reproducible steps is a systematic QA artifact that details exact user interactions causing a defect. It provides comprehensive evidence including screenshots and health scores to ensure engineering teams can reliably reproduce and address the issue.

Can I run regression checks on specific feature branches using automated QA?

Yes, you can run regression checks on specific feature branches by configuring the mode parameter to regression and specifying the target URL. This validates changed pages and interactions, outputting a structured QA report without modifying any code.

Does automated browser QA support pre-release verification for web applications?

Yes, automated browser QA supports pre-release verification by executing full or quick validation passes on the target web application. It verifies interactions, generates a health score, and outputs evidence under a designated QA reports directory to confirm release readiness.

How do I generate a test report with screenshots for web app bugs?

Generate a test report with screenshots by running an automated browser QA pass on your target URL. The workflow captures visual evidence, calculates a health score, and writes the structured artifacts with reproducible steps to a local output directory.

What are the limitations of report-only QA testing?

The primary limitation of report-only QA testing is that it never applies code fixes. It strictly generates structured artifacts with health scores and reproducible steps, requiring a separate engineering effort to resolve the identified defects.