qa-only

Test a web application and produce a structured QA report with health score, screenshots, and repro steps.

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

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

  • Automated QA reporting: Systematically tests a web app and outputs a health score, screenshots, and repro steps.
  • Evidence collection: Captures screenshots and logs to support bug reports.
  • No-fix policy: Ensures nothing is changed in the app during QA runs, directing to /qa for test-fix workflows.

Quick Start

Ask the QA skill to run a report on your web app and review the generated structured report.

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 any code changes?

You can run report-only QA testing to systematically evaluate a web app and output a structured report with health scores, screenshots, and repro steps without applying any code changes. It captures evidence and logs while ensuring nothing is modified in the application.

What is the best way to generate a bug report with screenshots and repro steps?

Generating a bug report with screenshots and repro steps is done via a report-only QA pass that systematically tests a web application and collects evidence. It captures screenshots and logs to support bug reports while enforcing a strict no-fix policy.

Does report-only QA testing work for comparing current web app behavior against a baseline?

Report-only QA testing does work for comparing current web app behavior against a baseline. It produces a structured report with health scores and reproducible steps to help you evaluate differences without triggering a full test-fix-verify loop.

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

You should use a report-only QA pass instead of a full test-fix-verify loop when you want to just report bugs or test but not fix anything. It directs you to a test-fix workflow only if you need to apply code changes and verify solutions.

What tools do I need to run automated QA reporting on a web application?

To run automated QA reporting on a web application, you need the Bash, Read, Write, AskUserQuestion, and WebSearch tools defined in the environment. These tools enable the skill to execute tests, capture evidence, and generate the structured report.