qa-only

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill qa-only-shekerkamma
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/shekerkamma/peopletech-marketplace/tree/main/plugins/gstack/qa-only
Command: npx skills add https://github.com/shekerkamma/peopletech-marketplace --skill qa-only-shekerkamma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of needing a structured, evidence-based quality assurance report for web applications without requesting automatic bug fixes, which is ideal for teams that separate testing and development workflows to avoid conflicts of interest and ensure clear handoffs.

Core Features & Use Cases

  • Real-User Testing: Simulates actual user behavior by clicking all interface elements, filling forms, and checking every app state to catch bugs real users would encounter.
  • Structured Reporting: Generates organized QA reports with a health score, annotated screenshots, and clear reproduction steps for every issue found.
  • Use Case: A product manager needs a bug report for a new checkout flow to share with the engineering team, with no automatic fixes attempted, so developers can prioritize and address issues on their own timeline.

Quick Start

Use the qa-only skill to run a full QA test of your web app at https://your-app.com and generate a structured bug report with health score and screenshots, without making any code changes.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I generate structured QA bug reports for a web app without applying code fixes?

To generate structured QA bug reports without code fixes, you need a report-only testing process that simulates user behavior and outputs health scores, annotated screenshots, and reproduction steps for developers.

What is regression testing for web applications and how does health scoring work?

Regression testing for web applications verifies that new changes haven't broken existing functionality. Health scoring works by evaluating the app's state during testing, assigning a metric to overall stability based on found bugs and usability issues.

How do I run ad-hoc bug reporting on a pre-release web application?

You can run ad-hoc bug reporting on a pre-release web application by executing a testing mode that clicks interface elements, fills forms, and captures annotated screenshots with reproduction steps for every issue encountered.

Can I configure the test scope and output directory for web app testing?

Yes, you can configure the test scope, test modes, and output directories for web app testing. This allows you to define the boundaries of the quality assurance test and specify exactly where the generated bug reports are stored.

Does QA testing require authentication credentials to test secure web app states?

QA testing supports optional authentication credentials to access secure web app states. Providing these credentials allows the testing process to simulate actual user behavior behind logins and check every app state for bugs.

When should I use a report-only QA workflow instead of automated bug fixing?

You should use a report-only QA workflow when your team separates testing and development to avoid conflicts of interest. It ensures clear handoffs with structured bug reports, letting developers prioritize and address issues independently.