qa-only

Identify UI and functional regressions in web apps and generate a QA report.

1|Updated Mar 1, 2026

Search Tags:#testing #screenshots #qa #evidence #web-app #bug-report #repro-steps

Ready to run

npx skills add https://github.com/anishs1207/agentic-cli --skill qa-only-anishs1207

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/anishs1207/agentic-cli/tree/main/.agents/skills/gstack-qa-only
Command: npx skills add https://github.com/anishs1207/agentic-cli --skill qa-only-anishs1207

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing to systematically test a web application and produce a structured quality-assurance report with health scoring, evidence, and reproducible steps — but never apply code changes.

Core Features & Use Cases

Thorough browser-based QA sessions that identify UI regressions and functional failures across pages.
Generates a structured report with health score, screenshots, console logs, and reproducible repro steps.
Use when asked to "just report bugs", "qa report only", or "test but don't fix"; for a full test-fix-verify loop, use /qa.

Quick Start

Run a lightweight QA pass on the target URL to produce a non-intrusive bug-report 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 a QA report for a web app without applying any code fixes?▼

To generate a report-only QA pass, you can run a non-intrusive testing session that identifies UI and functional regressions and outputs a structured bug report with health scoring, evidence, and repro steps without modifying the codebase.

What evidence is included in a structured bug report for UI regressions?▼

A structured bug report for UI regressions includes screenshots, console logs, and reproducible steps. It provides a health score and outputs both a JSON-like report and a markdown QA document for the tested web application.

How do I test dynamic web forms and navigation components for functional failures?▼

You test dynamic web forms and navigation components by performing thorough browser-based QA sessions that systematically interact with forms, navigation, and interactive components across multiple pages to identify functional failures.

Does this QA testing approach work for staging and development environments?▼

Yes, this QA testing approach applies to dynamic web apps in both development and staging environments. It focuses on identifying UI regressions and functional failures across pages while operating non-intrusively.

What is the difference between report-only QA testing and a full test-fix-verify loop?▼

Report-only QA testing systematically identifies bugs and generates a structured quality-assurance report with reproducible steps, but never applies code changes. A full test-fix-verify loop actively applies fixes after identifying the bugs.

Can I use this QA method to get a health score for my web application?▼

Yes, you can use this QA method to get a health score for your web application. The testing process evaluates forms, navigation, and interactive components, then outputs a structured report that includes the overall health score.