qa-only

Document web application defects through report-only QA testing without code changes.

2|1|Updated May 20, 2026

Search Tags:#testing #screenshots #qa #regression testing #browser testing #web application #bug reports

Ready to run

npx skills add https://github.com/balajivis/multiagent-primer --skill qa-only-balajivis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/balajivis/multiagent-primer/tree/main/lab0-workflow/gstack/qa-only
Command: npx skills add https://github.com/balajivis/multiagent-primer --skill qa-only-balajivis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams find and document web application defects systematically when they need a clear QA assessment without making any code changes.

Core Features & Use Cases

Report-Only Testing: Performs user-focused application testing and produces structured bug reports with evidence, health scores, screenshots, and reproduction steps.
Workflow Validation: Checks pages, navigation, forms, interactive elements, application states, and browser console issues across common testing scenarios.
Use Case: When a team needs an independent review before release, use this Skill to explore the application, capture reproducible issues, and create a detailed QA report while keeping the codebase untouched.

Quick Start

Ask the QA skill to test the web application and generate a bug report only without applying any fixes.

Frequently Asked Questions about qa-only

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

FAQPage Schema

How do I generate bug reports with reproduction steps without modifying application code?▼

Report-only QA testing systematically documents web application defects through structured evidence collection with screenshots, reproduction steps, and health scoring while keeping the codebase untouched.

What does non-invasive regression testing check during web application release validation?▼

Non-invasive regression testing checks pages, navigation, forms, interactive elements, application states, and browser console issues to produce structured bug reports for release validation.

How do I verify a feature branch using browser testing workflows?▼

Feature branch verification uses systematic browser-based usability testing to explore the application, capture reproducible issues, and generate detailed QA reports with health scores and screenshots.

When do I need report-only QA testing for my web application?▼

Report-only QA testing is needed when a team requires an independent review before release, providing a clear QA assessment and structured bug reports without making any code changes.

Can I perform usability testing and capture screenshots without applying fixes to the codebase?▼

Yes, you can perform user-focused application testing to capture screenshots and reproduction steps, generating thorough QA reports while safely keeping the codebase completely untouched.