qa-only

Generate a report-only QA test with health score, screenshots, and reproducible steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly generate a structured QA report for a web application without applying any fixes, including a health score, screenshots, and reproducible steps.

Core Features & Use Cases

  • Systematic, report-only QA testing that surfaces issues without code changes.
  • Structured reports with health scores, screenshots, and clear repro steps.
  • Use cases: when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa.

Quick Start

Run the qa-only skill to generate a full bug-report snapshot for your web app 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 bug report for a web application without applying any code fixes?

To generate a QA report without code fixes, run a report-only test. This process systematically surfaces web application issues and produces a structured bug report with a health score, screenshots, and reproducible steps.

What is included in a structured QA report for web applications?

A structured QA report includes a summarized health score, captured screenshots of the web application state, and clear reproducible steps for identified bugs. This provides a full bug-report snapshot without altering code.

How do I test my web application but ensure the tool does not modify my code?

To test without modifying code, request a "qa report only" task. This restricts the workflow to observing and documenting web application issues, ensuring your codebase remains untouched while still receiving a full bug report.

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

Use a report-only QA test when you need to quickly identify and document bugs for later review, such as requesting "just report bugs". Choose a full test-fix-verify loop when you want the process to apply fixes automatically.

Does a report-only QA test provide screenshots and reproducible steps for identified bugs?

Yes, a report-only QA test provides screenshots and reproducible steps. It systematically generates these elements alongside a health score to give developers a clear snapshot of the web application's state.