qa-only

Run on-demand QA passes and generate structured health reports with screenshots and reproducible steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA often requires time-consuming, repetitive tests every release. This Skill enables on-demand, manual-only QA reporting that does not modify the source code or apply fixes. It outputs a structured report with a health score, screenshots, and reproducible steps to help teams triage issues. Use when asked to "just report bugs", or when a non-fixing QA snapshot is sufficient.

Core Features & Use Cases

  • Manual trigger only: invoke QA reports on demand without changing code.
  • Structured health report: health score, screenshots, and reproducible steps.
  • Report-only workflow: no fixes are applied; designed for quick bug discovery and documentation.
  • Workflow compatibility: integrates with broader QA flows (e.g., '/qa') for deeper verification if needed.

Quick Start

Trigger a QA-only report by typing /qa-only to generate a report that documents bugs without applying 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 QA report for a web application without modifying the code?

A non-fixing QA report is a structured health snapshot that identifies bugs without modifying source code. It provides a health score, screenshots, and reproducible steps to help teams triage issues quickly during repetitive release cycles.

Can I run QA testing on new builds without applying automatic fixes?

Yes, you can execute reporting-only QA on new builds without applying fixes. This process runs a dedicated testing pass that produces a health score and artifacts, isolating bug discovery from code modifications.

What's the best way to document reproducible steps for bug triage?

The best way to document reproducible steps is to run an on-demand QA pass that automatically captures screenshots and generates structured reproduction steps. This ensures consistent bug documentation for team triage.

How do I trigger on-demand QA reporting for bug discovery?

You trigger on-demand QA reporting by invoking a manual slash command activation. This action executes a dedicated QA pass and emits a structured health report with artifacts for immediate bug discovery.

Does reporting-only QA integrate with broader verification workflows?

Yes, reporting-only QA integrates with broader verification workflows. The generated health score and artifacts can be passed to deeper QA flows for further verification when a more comprehensive analysis is needed.