qa-only

Test web applications and generate bug reports with health scores and reproduction steps.

Updated Jul 21, 2025
One-click install
npx skills add https://github.com/robertzengcn/aiFetchly --skill qa-only-robertzengcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/robertzengcn/aiFetchly/tree/main/.agents/skills/gstack/qa-only
Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill qa-only-robertzengcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of needing a structured, actionable bug report for web applications without requiring the AI to implement any fixes, which is ideal for handing off issues to development teams or documenting problems for later review.

Core Features & Use Cases

  • Structured Bug Reporting: Systematically tests web applications and generates reports with health scores, screenshots, and step-by-step reproduction instructions for every identified issue.
  • No-Fix Guarantee: Enforces a strict policy of only reporting bugs, never modifying code or implementing fixes, so you can trust the output won't alter your application.
  • Use Case: Use this Skill when running a QA pass on a new feature release and only need a list of bugs to send to your engineering team, with no immediate fixes required.

Quick Start

Use the qa-only skill to run a full QA test on your staging web app and generate a bug report with health scores and reproduction steps for all found 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 structured bug report for a web application without modifying code?

A report-only QA testing workflow generates structured bug reports for web applications without implementing fixes. It systematically identifies issues and outputs health scores, screenshots, and step-by-step reproduction instructions while enforcing a strict no-fix policy for safe handoff.

What is report-only QA testing and when do I need it for my staging web app?

Report-only QA testing is a non-destructive quality assurance workflow that identifies and documents web application bugs without applying fixes. You need it when running a QA pass on a new feature release to generate actionable bug reports for engineering teams.

Can I use automated QA testing to just find bugs and leave the fixes to developers?

Yes, report-only QA testing allows you to find bugs and leave fixes to developers. It enforces a strict no-fix guarantee, ensuring the testing process only produces standardized, actionable output like health scores and reproduction steps instead of modifying code.

What is the best way to document reproduction steps and health scores for web app bugs?

The best way to document reproduction steps and health scores is through standardized bug reporting. This method systematically tests web applications and generates actionable reports with step-by-step instructions and screenshots for every identified issue.

Does report-only QA testing alter my application code or configuration during the testing process?

No, report-only QA testing does not alter your application code or configuration. It enforces a strict no-fix policy that guarantees the workflow remains non-destructive, only documenting issues and producing actionable test output for later review.

How do I run a full QA pass on a staging web app and generate a list of bugs for my engineering team?

Run a full QA pass on a staging web app by applying report-only quality assurance testing. This generates a comprehensive bug report with health scores and reproduction steps for all found issues, providing standardized output specifically for engineering handoff.