qa-only

Generate a structured health report with evidence from web applications without code changes.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/zz8011/harnesstest --skill qa-only-zz8011
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/zz8011/harnesstest/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/zz8011/harnesstest --skill qa-only-zz8011

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces the cognitive load and time spent by testers by performing a focused QA pass that produces a structured report with health scores, screenshots, and reproducible steps, while ensuring no code changes are made.

Core Features & Use Cases

  • Performs report-only QA testing on web applications, producing a health score, screenshot evidence, and a reproducible bug narrative.
  • Useful when asked to "just report bugs", "qa report only", or for quick validation without fixes; complements full test-fix-verify loops with /qa.
  • Proactively suggests improvements only in the report, never modifies the source.

Quick Start

Run a QA pass on your web app to generate a structured bug report without applying any fixes.

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 structured QA report for a web application without modifying the source code?

Generate a structured QA report by running a read-only test pass on your web application that analyzes the interface and outputs a health score with evidence, ensuring no code changes are made. It uses built-in tooling to gather information and produce the standardized report.

What is the best way to perform a quick bug validation pass when a full test-fix-verify loop is not needed?

Perform a quick bug validation pass by executing a report-only QA test that produces a health score, screenshot evidence, and reproducible bug narrative without applying any fixes. This is ideal when asked to just report bugs or validate quickly.

Does the report-only QA testing approach include screenshots and reproducible steps in the output?

Yes, the report-only QA testing approach includes screenshot evidence and a reproducible bug narrative directly in the generated structured health report. This ensures testers have clear, documented proof of identified issues.

Can I use built-in Bash and WebSearch tools to automate web app QA report generation?

Yes, you can use built-in Bash, Read, Write, and WebSearch tools to gather information and automate web app QA report generation. These integrated tools drive the testing process to produce a standardized health report.

When should I not use a report-only QA pass for web application testing?

You should not use a report-only QA pass when you need to actually resolve bugs or modify code, as this approach proactively suggests improvements only in the report and never modifies the source. It complements, but does not replace, a full test-fix-verify loop.