qa-only

Analyze web applications and produce structured QA reports with screenshots and health scores.

Updated Apr 26, 2026

Search Tags:#testing #qa #web-app #bug-report #health-score #repro-steps

Ready to run

npx skills add https://github.com/XinheLIU/human-leverage --skill qa-only-xinheliu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/XinheLIU/human-leverage/tree/main/.claude/skills/qa-only
Command: npx skills add https://github.com/XinheLIU/human-leverage --skill qa-only-xinheliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testers often need to report issues without making any changes to the codebase. This skill generates a structured QA report with a health score, screenshots, and clear repro steps, ensuring that findings are organized and reproducible without fixes.

Core Features & Use Cases

Report-only testing: systematically simulates QA checks and produces an audit-style report for stakeholders.
Multi-mode operation: supports full, quick, and regression modes to match different sprint needs.
Evidence-rich outputs: includes screenshots, console observations, and an export-ready baseline for regression comparison.

Quick Start

Run a test pass by triggering the report-only flow against the current branch or a provided URL, then review the generated .gstack/qa-reports directory.

Frequently Asked Questions about qa-only

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

FAQPage Schema

How do I generate a bug report for a web app without changing the code?▼

To generate a bug report for a web app without changing the code, run a report-only QA pass to simulate checks, produce an audit-style report with health scores, and document per-page issues with screenshots and reproducible steps.

What is the best way to perform regression testing against a new git branch?▼

The best way to perform regression testing against a git branch is to run a regression mode QA pass that diffs the branch, prioritizes test plans from project folders or conversation context, and generates an exportable baseline for comparison.

How do I document QA issues with screenshots and health scores?▼

To document QA issues with screenshots and health scores, execute a full or quick mode testing pass that analyzes reachable web pages, logs session duration and outcomes, and outputs structured findings into an export-ready directory like .gstack/qa-reports.

Can I run a quick QA test pass against a specific base URL for my web application?▼

Yes, you can trigger a quick testing mode against a specific base URL or let the system auto-detect it, allowing you to rapidly simulate QA checks and produce structured reports with reference evidence for stakeholders.

Does report-only QA testing apply fixes to the codebase during analysis?▼

No, report-only QA testing never applies fixes to the codebase; it strictly analyzes the web application to produce structured documentation with per-page issues, health scores, and clear repro steps for developers to resolve.