qa-only

Generate structured QA reports with health scores, screenshots, and repro steps.

1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/geoffreywoo/clawfable --skill qa-only-geoffreywoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/geoffreywoo/clawfable/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/geoffreywoo/clawfable --skill qa-only-geoffreywoo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

QA engineers need to systematically test a web application and produce a structured report with evidence, without making any code changes. This skill ensures testers can generate reproducible steps, a health score, and visual evidence while leaving the product untouched for review.

Core Features & Use Cases

  • Report-only QA: runs automated checks and captures screenshots, logs, and a health score.
  • Structured output: produces a detailed QA report with reproducible steps, evidence, and a summary of findings.
  • Use cases: when a product team asks for a bug report without changes, or when you want to verify stability before a release.

Quick Start

Run a quick QA pass on the target app by telling the agent to start a QA-only session with /qa.

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 without altering code, use a report-only QA workflow that runs automated checks, captures screenshots, and logs reproduction steps. This non-intrusive approach produces a structured QA report while leaving the application state untouched.

How do I run a quick QA pass to check web app stability before a release?

You can run a quick QA pass to check web app stability by initiating a QA-only session using the /qa command. This automated process evaluates the application and outputs a health score alongside visual evidence to verify release readiness.

What is a web app health score and how does it work in automated testing?

A web app health score is a metric generated during automated QA testing that summarizes application stability. It works by running systematic checks across pages and combining the results into a structured score, giving teams a quick overview of product quality.

Can I perform regression-style checks on a web app without applying fixes?

Yes, you can perform regression-style checks without applying fixes by using a safe, report-only QA mode. This workflow focuses on capturing reproduction steps and evidence across pages to identify issues while ensuring the application state is never altered.

Where are QA testing reports and evidence stored?

QA testing reports and evidence are stored locally in the .gstack/qa-reports directory. This structured output includes reproduction steps, screenshots, and a summary of findings, keeping all testing results organized for later review.

Does report-only QA testing work for large web applications with multiple pages?

Report-only QA testing supports large web applications by systematically capturing evidence and reproduction steps across pages. It runs non-intrusive checks to calculate a comprehensive health score, ensuring thorough coverage without modifying the underlying product state.