skills.rest
ingoatl
ingoatlCOMMUNITY
Explore all skills by this author →
GitHub

qa-only

Run report-only QA testing on web applications and generate structured health reports.

Updated Aug 23, 2026
Search Tags:#testing#screenshots#qa#web-app#bug-report#health-score#repro-steps
One-click install
npx skills add https://github.com/ingoatl/propertycentral --skill qa-only-ingoatl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/ingoatl/propertycentral/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/ingoatl/propertycentral --skill qa-only-ingoatl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically tests a web application and produces a structured QA report with health score, screenshots, and repro steps — but never fixes anything.

Core Features & Use Cases

  • Performs a report-only QA pass to surface issues without applying any code changes.
  • Generates a structured health score, annotated screenshots, and clear repro steps to guide engineers.
  • Use when you want a precise, behavior-focused defect report without touching production or source code.

Quick Start

Run a report-only QA pass on your app to generate a formal bug-report document.

Frequently Asked Questions about qa-only

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

FAQPage Schema
What is report-only QA testing for web applications?▼

Report-only QA testing systematically evaluates web applications to identify bugs without modifying source code. It produces formal defect reports containing health scores, screenshots, and repro steps to guide engineering remediation.

How do I generate a bug report with repro steps for a web app?▼

Run a report-only QA pass on your web app to automatically generate a formal bug-report document. This process targets standard user flows and edge cases, producing structured health scores, annotated screenshots, and clear repro steps for remediation.

Can I run QA testing without applying code changes to production?▼

Yes, you can run report-only QA testing to surface issues without applying any code changes. It safely targets user flows and edge cases to produce a structured health report and repro steps, ensuring your production environment remains untouched.

What's the best way to document edge cases and standard user flows in testing?▼

The best way to document these flows is by running a report-only QA pass that targets both standard and edge cases. This generates a structured health report with annotated screenshots and clear repro steps to formally document behavior.

Does report-only QA provide a health score to help decide when to escalate issues?▼

Yes, report-only QA generates a structured health score alongside screenshots and repro steps. This provides safe guidance to help you decide precisely when to fix, escalate, or document the issues found during testing.

Related Skills

Explore More Software Engineering Skills→
iliasjennaneiliasjennane

playwright-explore-website

Explore websites to map user flows and generate Playwright-based tests.

Community
Intermediate
supertyrellesupertyrelle

bug

Extract artifact, symptom, repro steps, expected behavior, and severity into structured bug reports.

Community
Advanced
exiaoexiao
37

shots-pipeline

Orchestrate iOS screenshot capture, framing, and upload to App Store Connect.

Community
Advanced
uzumaki-incuzumaki-inc

qa-only

Generate a report-only web-app QA health report with score, screenshots, and reproduction steps.

Official
Advanced