qa-only

Name: qa-only
Availability: InStock
Author: kk20300113-png

Test web applications and generate structured QA reports with health scores and screenshots.

Updated May 9, 2026

Search Tags:#testing #quality assurance #qa #bug report #web application #screenshot #reproduction steps

Ready to run

npx skills add https://github.com/kk20300113-png/my-claude-skills --skill qa-only-kk20300113-png

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/qa-only
Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill qa-only-kk20300113-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of needing a thorough quality assessment of a web application without allowing the AI to make any code changes. It provides a structured bug report with health scores, screenshots, and reproduction steps while strictly enforcing a read-only testing boundary.

Core Features & Use Cases

Structured Bug Reporting: Generates comprehensive QA reports including health scores, screenshots, and step-by-step reproduction instructions.
Read-Only Enforcement: Never modifies code or attempts fixes, making it safe to run in production-like environments.
Use Case: A product manager needs to document all bugs found during a release candidate test without risking accidental code changes by the AI.

Quick Start

Use the qa-only skill to systematically test the web application and produce a structured report with health scores, screenshots, and reproduction steps without making any fixes.

Frequently Asked Questions about qa-only

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

Can I run quality assurance testing on a web application without modifying the code?▼

You can run quality assurance testing without modifying code by enforcing a read-only boundary. This approach systematically tests web applications to identify bugs and produces structured QA reports without applying any code fixes.

How do I generate a structured bug report with reproduction steps and screenshots?▼

To generate a structured bug report with reproduction steps and screenshots, systematically test the web application to identify bugs. This produces health scores, annotated screenshots, and reproducible step-by-step instructions for triage.

What is the best way to document bugs during a release candidate validation?▼

The best way to document bugs during release candidate validation is to run a read-only quality assessment. This generates comprehensive QA reports including health scores, screenshots, and reproduction steps while strictly preventing accidental code changes.

Does read-only bug reporting work for regression testing in production-like environments?▼

Read-only bug reporting works safely for regression testing in production-like environments. It never modifies code or attempts fixes, making it secure for systematically testing web applications and producing structured triage reports.

How do I perform a pure bug triage without the AI attempting to fix the issues?▼

To perform a pure bug triage without AI fixes, use a read-only testing boundary that strictly enforces no code changes. This systematically identifies bugs and produces structured QA reports with health scores and reproduction steps.