qa-only

Test web applications and generate structured QA reports with health scores.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes.

Core Features & Use Cases

  • Systematically tests a web application and produces a structured health report with screenshots and repro steps.
  • Never changes or fixes bugs; only reports.
  • Supports the /qa workflow and uses "qa" command to run full test-fix-verify loops.

Quick Start

Ask me to run /qa with a target URL and I will start a browser-based QA pass that reports findings without fixes.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I run QA testing on a web app without applying code fixes?

Report-only QA testing detects and reports defects in a web application through user-like testing, producing structured reports with health scores, screenshots, and repro steps without applying fixes.

What is the best way to generate a QA regression report for a staging URL?

Targeting a staging URL with regression baseline support generates a structured QA report capturing evidence, health scoring, and repro steps for functional flows and UI states.

Does report-only QA testing work with feature branches and diff-aware options?

Yes, report-only QA testing supports diff-aware options when running on feature branches, enabling targeted defect detection and evidence capture across local or staging URLs.

Do I need a browser automation tool to test web app navigation and forms?

Yes, detecting defects in functional flows, forms, and navigation requires a browser automation tool to simulate user-like interactions and capture UI state evidence.

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

Use report-only QA testing when you need to systematically identify and document bugs with screenshots and health scores without committing code changes, leaving fixes for a separate workflow.