qa-only

Run a report-only QA pass on a web application and generate a structured bug report.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/Liambiswell20-tech/Bolus-Brain --skill qa-only-liambiswell20-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/Liambiswell20-tech/Bolus-Brain/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/Liambiswell20-tech/Bolus-Brain --skill qa-only-liambiswell20-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA testing by generating structured reports without applying fixes, enabling quick bug visibility and triage.

Core Features & Use Cases

  • Systematically tests a web application and produces a structured report with a health score, screenshots, and reproduction steps.
  • Never fixes anything; use /qa for the full test-fix-verify loop.
  • Useful for audits, contract QA, and status reporting.

Quick Start

Run a report-only QA pass against the target web app to generate a structured assessment without making changes.

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 applying fixes?

A report-only QA pass systematically tests a web application to produce a structured assessment without making changes. It collects full-screen screenshots, health scores, and reproduction steps for quick bug visibility and triage.

What is included in a structured QA health score report for web applications?

A structured QA health score report includes full-page screenshots, detailed reproduction steps, and a calculated health score. It systematically assesses the web app environment to provide quick visibility into bugs for triage.

How do I run a report-only QA pass on a specific testing target URL?

To run a report-only QA pass, provide the testing target URL or environment. The process systematically tests the web app across pages and generates a standardized report with screenshots and repro steps without performing fixes.

When should I use a report-only QA pass instead of a full test-fix-verify loop?

Use a report-only QA pass for audits, contract QA, or status reporting where you need bug visibility without code changes. If you need to apply corrections, use the full test-fix-verify loop via /qa instead.

Does the QA report generation process modify the web application code?

The QA report generation process never modifies the web application code. It strictly performs a non-fix loop to identify bugs and collect screenshots, health scores, and repro steps for the final standardized report.