qa-only

Run non-fix QA tests on web applications and generate structured bug reports.

Updated Mar 19, 2026

Search Tags:#testing #screenshots #qa #evidence #web-app #bug-report

Ready to run

npx skills add https://github.com/shaneholloman/ship --skill qa-only-shaneholloman

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? QA teams and developers need a deterministic, non-destructive way to discover and document issues in web apps. This skill provides repeatable testing that outputs a structured report with evidence (screenshots, logs, and repro steps) without performing any code changes or fixes.

## Core Features & Use Cases

Systematic manual-style QA where every page and interaction is checked with evidence captured.
Structured reporting that includes health indicators, screenshots, and repro steps without applying fixes.
Works across diff-based or full-app testing contexts, with support for setup and test plan interpretation.

### Quick Start Run a report-only QA pass on a web app to generate a structured bug findings report.

Frequently Asked Questions about qa-only

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

FAQPage Schema

How do I generate QA testing reports with screenshots and console logs for a web app?▼

Automated QA testing reports for web apps are generated by running a non-destructive testing pass that captures screenshots, console logs, and reproducible steps into a structured findings document without applying fixes.

What is non-destructive QA testing and how does it document bug findings?▼

Non-destructive QA testing systematically surfaces issues in web applications by capturing evidence like screenshots and repro steps, outputting a structured bug report without modifying or fixing the underlying codebase.

Can I run QA testing on specific Git branches instead of the full web application?▼

Yes, QA testing supports diff-aware branch testing to target specific changes, alongside full-app exploration. Both modes systematically check interactions and capture evidence-backed documentation for reproducible issues.

Does report-only QA testing automatically fix the bugs it discovers?▼

No, report-only QA testing strictly focuses on discovering and documenting issues. It produces structured reports with health indicators and evidence without performing any code changes or applying fixes to the web application.

What do I need to provide to run an automated QA testing pass for structured bug reports?▼

You need to provide the web application context and required assets for testing. The skill interprets your setup and test plan to systematically check pages and interactions, capturing evidence for the final structured report.