qa-only

Test a web application and generate a structured QA report with health score, screenshots, and reproducible steps.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/FxHollow/100000mrr-landing --skill qa-only-fxhollow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/FxHollow/100000mrr-landing/tree/main/.agents/skills/gstack/qa-only
Command: npx skills add https://github.com/FxHollow/100000mrr-landing --skill qa-only-fxhollow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing eliminates the need to apply changes while verifying a web application, producing a structured health score, evidence, and reproducible steps for bug reporting.

Core Features & Use Cases

  • Systematically tests a web app and produces a structured report with health score, screenshots, and reproducible steps.
  • Use when asked to "just report bugs", "qa report only", or "test but don't fix". For a full test-fix-verify loop, use /qa.
  • Proactively suggest bug reports without any code changes when appropriate.

Quick Start

Ask the QA-only skill to run a report on the current web app state and 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 QA report without applying any code fixes?

To generate a QA report without applying fixes, automate non-fixing QA testing to produce a structured report with a health score, screenshots, and reproducible steps for bug reporting.

What is non-fixing QA testing and when do I need it?

Non-fixing QA testing systematically evaluates a web application and proactively suggests bug reports without modifying the codebase. You need it when you want to verify application health and document issues separately from the resolution process.

Can I get screenshots and reproducible steps for bug reports automatically?

Yes, you can automatically capture screenshots and generate structured reproducible steps by running a report-only QA test on your current web application state to document bugs.

Does report-only QA testing support a full test-fix-verify loop?

Report-only QA testing focuses exclusively on documenting issues without code changes, but it can guide a full test-fix-verify loop using a separate command when you are ready to apply fixes.

When should I avoid using an automated bug report only approach?

You should avoid using a bug report only approach when your goal requires immediate code modifications, as this testing method proactively suggests bug reports but strictly does not perform any automatic fixes.