qa-only

Run report-only QA tests on web applications and collect screenshots, console errors, and a health score.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It lets you verify that a web app works as expected by systematically testing what a real user would do, while producing a clear, structured bug report.

Core Features & Use Cases

  • Manual trigger report-only QA: Runs only when you explicitly invoke /qa-only, with a strict “never fix” guarantee.
  • Structured findings with evidence: Captures screenshots, console errors, and reproducible steps for each issue you hit.
  • Scoring and coverage: Computes a health score (console, links, visual, functional, UX, performance, content, and accessibility) and summarizes the top issues.

Use it when you need to answer “What’s broken?” or “Please just generate a QA report,” especially after a change that might have introduced regressions.

Quick Start

Tell the skill: "Run /qa-only against http://localhost:3000 and produce a structured report with screenshots and repro steps, but do not fix anything."

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 with repro steps and screenshots for a web app?

Generate a QA report by triggering a browser-based test that navigates UI flows and submits forms to collect screenshots, console errors, and reproducible steps. The output is a structured report with a health score that strictly verifies issues without applying any code fixes.

What is regression verification for web apps and when do I need it?

Regression verification for web apps systematically checks if recent changes broke existing functionality by navigating UI flows and checking states. You need it after updates to quickly identify what is broken, capturing evidence like console errors and screenshots to ensure no new issues were introduced.

Can I run browser testing to collect console errors without modifying my code?

Yes, you can run browser testing to collect console errors without modifying code. The testing process interacts with the web application purely to capture evidence like screenshots and repro steps, operating under a strict guarantee that it never edits code or applies fixes.

What's the best way to check web app health scoring after a feature update?

The best way to check web app health scoring is to run a report-only QA test that computes scores across console, links, visual, functional, UX, performance, content, and accessibility dimensions. This summarizes top issues and provides structured evidence without altering the application code.

How do I get screenshot evidence and structured bug reports for UI flows?

Get screenshot evidence and structured bug reports by running a browser-based test that navigates UI flows, submits forms, and checks application states. The process automatically captures visual evidence and console errors to produce a clear, structured report of the issues encountered.

Does report-only QA testing support quick verification scenarios for local web apps?

Yes, report-only QA testing supports quick verification scenarios for local web apps. It applies to full, quick, and regression-style checks, allowing you to target a local URL to systematically test real user interactions and output a structured health report with evidence.