qa-only

Automate web application testing and generate QA reports with health scores and screenshots.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/ericdahl-dev/coauthor-cleaner --skill qa-only-ericdahl-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/ericdahl-dev/coauthor-cleaner/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/ericdahl-dev/coauthor-cleaner --skill qa-only-ericdahl-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill unit "qa-only" automates the systematic testing of web applications, providing detailed reports including health scores and repro steps without implementing fixes.

Core Features & Use Cases

  • Systematic Web Testing: Automated testing for health score assessment, screenshots, and repro steps.
  • No Bug Fixing: Ideal for generating comprehensive QA reports when code changes are not required.
  • Use Case: For developers looking to report issues found in web applications but not engage in immediate fixing or bug resolution.

Quick Start

Use the /qa-only command to generate a report on your web application issues.

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 web application QA report with a health score?

To generate a web application QA report with a health score, you can use automated systematic testing to evaluate the application, producing comprehensive assessment details and screenshots without implementing fixes.

What is the best way to perform QA testing on a web application without fixing bugs?

The best way to perform QA testing without fixing bugs is to use a structured reporting approach that focuses on issue assessment, generating detailed reports with health scores and repro steps instead of code changes.

Can I get automated screenshots and repro steps for web application issues?

Yes, automated systematic web testing can capture screenshots and generate reproduction steps for application issues, providing a detailed QA report for developers without requiring immediate bug resolution.

Does this systematic testing approach implement code changes during bug reporting?

No, this systematic testing approach does not implement code changes. It is designed specifically for generating comprehensive QA reports and health score assessments without engaging in bug fixing.

When do I need to use a health score assessment for my web application?

You need to use a health score assessment when you want a comprehensive evaluation of your web application's issues, allowing developers to report problems systematically without engaging in immediate fixes.