skills.rest
tyhuffman7
tyhuffman7COMMUNITY
Explore all skills by this author →
GitHub

qa-only

Run read-only QA tests and generate a structured bug report with health score, screenshots, and repro steps.

1|Updated Apr 15, 2026
Search Tags:#testing#qa#web-application#bug-report#health-score#repro-steps
One-click install
npx skills add https://github.com/tyhuffman7/gstack-hermes --skill qa-only-tyhuffman7
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/tyhuffman7/gstack-hermes/tree/main/gstack-qa-only
Command: npx skills add https://github.com/tyhuffman7/gstack-hermes --skill qa-only-tyhuffman7

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack)

Core Features & Use Cases

  • Read-only QA passes that identify bugs and edge cases without applying code changes
  • Produces a structured report including a health score, screenshots, and reproducible steps
  • Useful for release readiness, bug triage, and compliance checks; can point to /qa for full test-fix-verify

Quick Start

Run the qa-only pass to generate a report 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 applying code fixes?▼

To generate a QA report without fixing bugs, run a read-only testing pass that interacts with the UI, captures screenshots, and exports a structured report with a health score and repro steps.

What is read-only QA testing and when should I use it?▼

Read-only QA testing systematically identifies bugs and edge cases in a web application while producing a health score report, used for release readiness, bug triage, and compliance audits without making code changes.

Can I use this for release readiness checks if I only need a bug report?▼

Yes, you can use report-only QA testing for release readiness checks to gain visibility into bugs through a structured report with screenshots and repro steps, ensuring no code modifications are applied during the audit.

What is the best way to document web application bugs with reproducible steps?▼

The best way to document bugs without fixing them is using a report-only QA test that systematically interacts with the UI to produce a structured report containing a health score, screenshots, and detailed repro steps.

Do I need a test harness to capture screenshots and export a structured QA report?▼

Yes, you need a test harness capable of interacting with the web application UI, capturing screenshots, and exporting a report in a stable format to successfully generate the structured QA report with repro steps.

Why should I choose report-only QA testing instead of a full test-fix-verify loop?▼

Choose report-only QA testing when you need a structured bug report with a health score for audits or quick reviews, but want to avoid applying code changes; use the full test-fix-verify loop when you want bugs automatically resolved.

Related Skills

Explore More Software Engineering Skills→
ShaheerKhawajaShaheerKhawaja
8

browse

Automate headless browser QA tasks with navigation, screenshots, and element interaction.

Community
Intermediate
chriswesttchriswestt

qa-only

Run report-only QA testing on web applications and generate health scores, screenshots, and repro steps.

Community
Intermediate
SakshamKandelSakshamKandel

qa-only

Test a web application and produce a structured bug report with health score, screenshots, and repro steps.

Community
Advanced
gil-kapelgil-kapel
2

debug

Collects logs, environment details, and code changes to diagnose issues during manual testing or implementation scenarios.

Community
Intermediate