qa-only

Execute automated checks and manual validation on web apps to generate structured QA reports.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/makyua-san/usecase-agent --skill qa-only-makyua-san
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/makyua-san/usecase-agent/tree/main/.claude/skills/qa-only
Command: npx skills add https://github.com/makyua-san/usecase-agent --skill qa-only-makyua-san

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The QA workflow lets teams systematically test a web app and produce a consistent, structured bug report that includes a health score, visual evidence, and reproducible steps, without applying any code changes.

Core Features & Use Cases

  • Automated health scoring and visual regressions capture
  • Repro steps with clear guidance for developers
  • Use Case: run a quick pass on a new build to surface critical issues before staging

Quick Start

Run a full QA pass on the target web application and generate a structured bug report with health score and repro steps.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I run a QA pass and generate a structured bug report for a web app?

A QA pass systematically tests a web app by executing automated checks and manual validation. It generates a structured bug report containing a health score, screenshots, and reproducible steps to document findings without applying fixes.

What is a web app health score and how does visual regression capture work?

A web app health score quantifies application stability during QA testing, while visual regression capture screenshots the target application to identify UI defects. These metrics are compiled into a structured report to surface critical issues before staging.

Can I use automated checks for release verification across staging and production?

Automated checks support release verification across development, staging, and production environments. They validate the target web app to surface critical issues, capturing screenshots and health scores to ensure consistent quality before deployment.

Does this QA testing approach apply code fixes or modify the web app?

This QA testing approach enforces a strict no-fix policy and does not apply code fixes or modify the web app. It strictly documents findings, visual evidence, and reproducible steps in a standard format to keep fixes out of scope.

What is the best way to surface critical issues before staging a new build?

The best way to surface critical issues before staging is to run a quick QA pass on the new build. This executes targeted automated checks and manual validation to capture health scores and generate structured bug reports for developers.