qa-only

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

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill qa-only-sakshamkandel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/SakshamKandel/Salt-Route-Consulting-/tree/main/.agents/skills/qa-only
Command: npx skills add https://github.com/SakshamKandel/Salt-Route-Consulting- --skill qa-only-sakshamkandel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything.

Core Features & Use Cases

  • Systematic, readout-focused QA that outputs a health score, screenshots, and reproducible steps for bugs.
  • Supports "just report bugs" / "qa report only" workflows to avoid making changes, while still surfacing actionable insights.
  • For a full test-fix-verify loop, use the dedicated /qa workflow in your testing harness.

Quick Start

Trigger a QA-only report for the current web app to generate a structured bug report without applying any code changes.

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 app without applying any code fixes?

A QA report only workflow systematically tests your web app and outputs a structured report with health scores, screenshots, and repro steps while never modifying your codebase, ensuring you just report bugs without applying fixes.

What is a structured QA report and what does it include?

A structured QA report provides a systematic readout of web application health, delivering an overall health score, annotated screenshots, and detailed reproducible steps for identified bugs to surface actionable testing insights.

Can I run automated testing that only reports bugs and skips the fix-verify loop?

Yes, you can run automated testing that only reports bugs by triggering a workflow designed to avoid making changes, skipping the full test-fix-verify loop to focus entirely on surfacing and documenting issues.

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

Use a report-only QA workflow when asked to just report bugs or when needing an assessment without code changes. Switch to a full test-fix-verify loop when you want the testing harness to automatically resolve identified issues.

Does report-only QA testing provide reproducible steps for bug reporting?

Yes, report-only QA testing provides reproducible steps for bug reporting by systematically testing the web application and generating a structured readout ensuring every surfaced bug includes detailed reproduction instructions.

What are the limitations of running QA testing without fixing code?

The limitation of QA testing without fixing code is that identified bugs remain unresolved. This approach strictly produces a structured report with health scores and screenshots, meaning a separate effort is required to implement fixes.