Verified:GitHub

qa-only

Name: qa-only
Availability: InStock
Author: apeejay-education

Analyzes a web application and generates a structured bug report with health score, screenshots, and repro steps without modifying code.

1|Updated Mar 26, 2026

Search Tags:#automation #testing #screenshots #qa #web-app #bug-report #health-score

Ready to run

npx skills add https://github.com/apeejay-education/cadencesprout --skill qa-only-apeejay-education

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/apeejay-education/cadencesprout/tree/main/.agents/skills/gstack-qa-only
Command: npx skills add https://github.com/apeejay-education/cadencesprout --skill qa-only-apeejay-education

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing that systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything.

Core Features & Use Cases

Systematic web-app testing that generates a health score, evidence screenshots, and reproducible steps.
Non-intrusive QA: reports issues without applying fixes, leaving the codebase untouched.
Use Case: when you need a clear bug report for handoff or QA review, or to accompany a product release.

Quick Start

Run qa-only to perform report-only QA testing and generate a structured bug 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 a structured bug report for a web application without modifying code?▼

Report-only QA testing analyzes a web application to generate a structured bug report without applying fixes. It captures a health score, evidence screenshots, and reproducible steps, leaving the codebase untouched for safe handoff.

What is non-intrusive QA testing and when do I need it?▼

Non-intrusive QA testing systematically tests a web application to report issues without applying fixes. You need it when a clear, actionable bug narrative is required for documentation-ready QA reports or pre-release testing.

Can I capture evidence screenshots and reproducible steps for pre-release testing?▼

Yes, you can capture evidence screenshots and reproducible steps for pre-release testing by running automated tests on a web application. The process generates a health score and structured bug report to accompany your release.

Does this automated testing approach apply fixes to the codebase?▼

No, this automated testing approach does not apply fixes to the codebase. It is designed for non-intrusive QA to generate a structured bug report with a health score and screenshots, leaving the code untouched.

What's the best way to document a web-app health score for QA handoff?▼

The best way to document a web-app health score for QA handoff is using report-only testing to automate tests and capture screenshots. It produces a structured bug report with reproducible steps for clear review.