qa-only

Run a report-only QA pass generating a health score, screenshots, and reproducible steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web apps often ship with bugs but teams still want rapid visibility without creating fix cycles. This skill provides a deterministic, report-only QA pass that yields a structured health score, curated screenshots, and reproducible steps—without applying any code changes.

Core Features & Use Cases

  • Systematic web QA pass that reports issues, not fixes.
  • Produces a health score, screenshots, and detailed repro steps for triage.
  • Use when you want to audit quality before releases or during learnings without touching code.

Quick Start

Run a report-only QA pass to generate the health report, screenshots, and reproducible steps.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I run a web app QA pass that only reports bugs without changing code?

To run a report-only QA pass, trigger a systematic scan of your web app. This generates a structured readout with a health score, screenshots, and repro steps, ensuring no code changes are applied.

What is a report-only QA pass and when should I use it?

A report-only QA pass systematically audits a web application to yield a health score, screenshots, and reproducible steps. Use it when you need rapid visibility into bugs before releases without triggering fix cycles.

Can I get structured bug reports with repro steps for my web app?

Yes, you can generate structured bug reports by running a report-only QA pass. It produces detailed repro steps and a health score for triage, helping you track issues without modifying your workflow.

Does this QA tool apply code fixes during its web app health check?

No, this QA tool never applies fixes during a web app health check. It operates strictly as a report-only mechanism, providing a structured readout of issues, screenshots, and repro steps.

What is the best way to audit web app quality before a release without touching code?

The best way to audit quality without touching code is a report-only QA pass. It systematically evaluates your web app and outputs a health score, screenshots, and repro steps for triage.

Are there limitations to using a report-only workflow for web app testing?

The main limitation of a report-only QA workflow is that it generates a health score and bug repro steps but never applies fixes. You must implement separate code changes to resolve the reported issues.