qa-only

Document web app bugs with health scores, screenshots, and repro steps.

20|3|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/Walrus-Computing/piper-draw --skill qa-only-walrus-computing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/Walrus-Computing/piper-draw/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/Walrus-Computing/piper-draw --skill qa-only-walrus-computing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

qa-only runs a web app test pass when you need bugs found, documented, and handed off without any code changes or fixes.

Core Features & Use Cases

  • Report-only testing: Checks app behavior and records issues instead of editing files.
  • Structured bug reports: Captures health scores, screenshots, and reproduction steps in one pass.
  • Best for handoff: Use it after a release, during regression checks, or when a stakeholder wants proof of what is broken.

Quick Start

Ask the qa-only skill to test the app and return a bug report with screenshots, health score, and repro steps only.

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 with screenshots and repro steps for a web app?

You can run a report-only QA assessment to document web app bugs with health scores, screenshots, and repro steps in one pass without altering your codebase.

What is report-only web testing and when do I need it?

Report-only web testing is a QA process that checks application behavior and documents issues without applying fixes, ideal for regression checks or handing off documented bugs to developers.

Can I use this approach for manual verification after a release without changing code?

Yes, manual verification after a release can be performed using a report-only QA pass to document findings and health scores while explicitly avoiding any code fixes or file edits.

Does this QA method include a health score for the application being tested?

Yes, the QA method includes a structured health score for the web application being tested, alongside captured screenshots and reproduction steps, to provide a clear assessment of app stability.

What are the limitations of a report-only bug hunting approach?

The limitation of a report-only bug hunting approach is that it strictly documents issues and captures reproduction steps without implementing fixes, requiring a separate workflow to resolve the bugs.