qa-only

Test web applications and generate bug reports with health scores and screenshots.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/a29paul/hexlens --skill qa-only-a29paul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/a29paul/hexlens/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/a29paul/hexlens --skill qa-only-a29paul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the need to split attention between finding web application bugs and fixing them, perfect for teams that separate QA and development responsibilities or need fast bug audits without code changes.

Core Features & Use Cases

  • Systematic Web App Testing: Clicks every interactive element, fills all form fields, and checks every user flow state to catch hidden bugs that manual testing misses.
  • Structured Bug Reports: Generates reports with overall health scores, annotated screenshots, and step-by-step reproduction instructions for every issue found.
  • Use Case: If your team needs a pre-launch bug audit for a new client onboarding portal, this skill will run through every user path, document broken links and form errors, and deliver a shareable report without touching any code.

Quick Start

Use the qa-only skill to test the staging site at https://staging.myapp.com and generate a bug report focused on the user login flow.

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 bug report for web applications without modifying any code?

Report-only QA testing systematically checks web application user flows, interactive elements, and form fields to document bugs with health scores and annotated screenshots. It produces structured issue documentation without implementing any code fixes or modifications.

What is report-only QA testing and when do I need it for pre-launch health checks?

Report-only QA testing is a quality assurance process that audits web applications to identify and document bugs without applying fixes. You need it for pre-launch health checks, regression testing, or bug audits where only structured issue documentation is required.

Can I use automated QA testing to document broken links and form errors for a staging site?

Yes, automated QA testing can systematically click interactive elements and fill form fields on your staging site to catch broken links and form errors. It delivers a shareable structured bug report with overall health scores, annotated screenshots, and step-by-step reproduction instructions.

What is the best way to perform a bug audit for a new client onboarding portal?

The best way to perform a bug audit for a client onboarding portal is to run systematic web application testing across every user path. This documents broken links, form errors, and hidden bugs into a structured report with health scores without touching the codebase.

Does structured bug reporting include reproducible steps and screenshots for every issue found?

Structured bug reporting does include step-by-step reproduction instructions and annotated screenshots for every issue found. It also provides overall health scores to quantify the web application's quality status during the QA testing process.

What are the limitations of report-only bug audits for web applications?

The main limitation of report-only bug audits is that they explicitly avoid implementing any code fixes or issue resolution. This means your development team must separately review the generated structured reports and manually resolve the documented web application bugs.