qa-only

Run a deterministic test suite and generate a read-only QA report with health scores.

2|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/nicholaslocascio/x-claw-studio --skill qa-only-nicholaslocascio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/nicholaslocascio/x-claw-studio/tree/main/skills/gstack/qa-only
Command: npx skills add https://github.com/nicholaslocascio/x-claw-studio --skill qa-only-nicholaslocascio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams need a consistent, reproducible way to assess a web application's health and surface issues without making any changes to the codebase.

Core Features & Use Cases

  • Structured, read-only health reports that include reproducible steps, screenshots, and a formal bug narrative.
  • Deterministic test execution using a predefined plan to ensure repeatable results across environments.
  • Transparent, non-destructive assessment: findings are documented but not fixed, enabling clear handoffs to development teams.

Quick Start

Run the qa-only workflow to generate a reproducible QA report for the current application.

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 read-only QA report for a web application?

You can generate a read-only QA report by running a deterministic test suite against your web application. The workflow analyzes behavior and outputs structured health scores, reproducible steps, and screenshots without applying any code fixes.

Can I run automated QA testing without modifying the codebase?

Yes, automated QA testing can run in a strictly read-only mode. It assesses application stability and identifies regressions by documenting findings and capturing screenshots, ensuring the codebase remains completely unmodified during the assessment.

What is a deterministic test suite for web application health scoring?

A deterministic test suite is a predefined testing plan that ensures repeatable results across environments. It executes consistent test scenarios to verify application stability, calculate health scores, and surface issues for triage.

How do I document reproducible steps and screenshots for bug triage?

You can document bugs by executing a predefined testing plan that automatically captures screenshots and formal bug narratives. This process generates a structured report with detailed repro steps, enabling clear handoffs to development teams.

Does QA reporting work without applying automatic fixes to the code?

Yes, this QA reporting approach is explicitly designed to never apply fixes. It operates non-destructively, transparently documenting application issues, regressions, and formal bug narratives for development teams to review and resolve independently.

When should I use a report-only QA workflow instead of automated fixing?

Use a report-only QA workflow when you need a consistent, reproducible way to surface issues for triage without altering the codebase. It is ideal for transparent assessments where findings must be documented for development handoffs rather than resolved automatically.