qa-only

Run report-only QA testing on web applications and generate structured health reports with evidence.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/alexandervashurin/semaphore --skill qa-only-alexandervashurin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/alexandervashurin/semaphore/tree/main/.claude/skills/qa-only
Command: npx skills add https://github.com/alexandervashurin/semaphore --skill qa-only-alexandervashurin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing eliminates the need to fix defects while surfacing issues in a web app, producing a structured health report with evidence such as screenshots and repro steps.

Core Features & Use Cases

  • Structured QA reports including health score, screenshots, and repro steps
  • Non-fix loop: surface bugs without making code changes
  • Diff-aware and full exploration modes to verify recent changes

Quick Start

Run /qa-only on your web app to generate a structured, fix-free QA report.

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 app without modifying the code?

Report-only QA testing generates a structured health report for a web app without applying any code fixes. It surfaces issues and collects evidence like screenshots and repro steps in a non-fix loop.

What is a non-fix loop in web app testing?

A non-fix loop in web app testing surfaces defects and collects evidence, such as screenshots and repro steps, without making any code changes. This approach ensures issues are documented in a structured health report rather than automatically patched.

Can I run QA testing that produces screenshots and repro steps for recent changes?

Yes, QA testing can produce screenshots and repro steps for recent changes. The process supports diff-aware exploration modes to verify recent updates and generate a structured health report with evidence.

How do I get a health score across pages during web app QA testing?

You can get a health score across pages by running a QA testing process on your web app. This generates a structured health report that includes the score alongside evidence like screenshots and repro steps.

Does report-only QA testing allow configurable output directories and report templates?

Yes, report-only QA testing satisfies requirements for configurable output directories and report templates. This allows you to specify where the structured health report and its evidence are saved.

When should I use a non-fix QA testing approach instead of automated fixing?

Use a non-fix QA testing approach when you want to surface bugs and collect evidence in development or QA contexts without applying fixes. It is ideal when you need to document issues via a health report before resolving them.