qa-only

Run report-only QA testing on web applications and generate health reports with screenshots and reproducible steps.

Updated Dec 13, 2017
One-click install
npx skills add https://github.com/dogeared/tnra --skill qa-only-dogeared
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/dogeared/tnra/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/dogeared/tnra --skill qa-only-dogeared

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing eliminates the tedious cycles of bug triage by producing a structured health report with evidence, screenshots, and reproducible steps without applying any code changes.

Core Features & Use Cases

  • Systematic web app testing that documents findings instead of fixes.
  • Generates a health score, screenshots, and a repro-step narrative to hand off to developers or stakeholders.
  • Use cases include quick QA handoffs, regression triage, and audit-ready test documentation.

Quick Start

Run the QA-only workflow against your target app to generate the structured report with health score, evidence, and reproducible steps.

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?

Report-only QA testing evaluates a web application and outputs a structured health report with screenshots and reproducible steps, strictly avoiding code changes. It is designed for scenarios where you need to just report bugs and hand off documentation to developers.

Does automated QA testing always modify the codebase during bug triage?

No, report-only QA testing performs a non-intrusive evaluation that documents findings instead of fixes. It generates an audit-ready health score and narrative without touching the codebase, unlike full test-fix-verify loops that implement changes.

What's the best way to document reproducible steps and screenshots for a regression triage?

Running a report-only QA workflow automates the documentation of regression triage by generating a comprehensive health report. This report includes evidence, screenshots, and a repro-step narrative ready for stakeholder handoff.

Can I get a health score for my web application without altering the source code?

Yes, report-only QA testing calculates a health score by systematically evaluating your web application. It yields an audit-ready health report with evidence without implementing any fixes or altering the source code.

When should I use a report-only QA workflow instead of a full test-fix-verify loop?

Use a report-only QA workflow when you need quick QA handoffs, regression triage, or audit-ready test documentation. It remains focused on non-intrusive reporting, whereas a full test-fix-verify loop via /qa is better when you want bugs automatically resolved.