qa-only

Run report-only QA tests on web applications and generate structured bug reports.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/CaltexBevo/ihe-pulse --skill qa-only-caltexbevo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/CaltexBevo/ihe-pulse/tree/main/.claude/skills/gstack.bak/qa-only
Command: npx skills add https://github.com/CaltexBevo/ihe-pulse --skill qa-only-caltexbevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing helps teams systematically verify a web application and produce a structured bug report without performing any fixes.

Core Features & Use Cases

  • Systematic QA tests that generate a health score, capture screenshots, and include repro steps, all without changing code.
  • Designed for prompts like "just report bugs" or "qa report only"; for the full test-fix-verify loop, use /qa.

Quick Start

Run a report-only QA pass on the target app.

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 QA report for a web application without fixing the bugs?

To generate a QA report without fixing bugs, you can run a report-only QA test that systematically verifies a web application and produces a structured report with a health score, screenshots, and repro steps without applying any fixes.

What is a report-only QA test and when do I need it?

A report-only QA test systematically verifies a web application to document issues and generate a structured bug report without modifying code. You need it when you want to separate issue documentation from the actual test-fix-verify loop.

Can I capture screenshots and repro steps during automated QA testing?

Yes, automated QA testing can capture screenshots and include repro steps in a structured report. This process systematically verifies the web application and calculates a health score to quantify the application's current state.

Does report-only QA testing apply code fixes to the web application?

No, report-only QA testing does not apply any code fixes. It strictly documents issues and produces a structured report with a health score, screenshots, and repro steps, leaving the actual test-fix-verify loop to a separate process.

What is the best way to document web application bugs for a separate team to fix?

The best way to document web application bugs is using a report-only QA pass that generates a structured report including a health score, screenshots, and detailed repro steps, ensuring the fixing team has all necessary context without altering the codebase.