qa-only

Identify and document web application defects with reproducible steps and screenshots.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables report-only QA testing for web applications, generating a structured bug report that includes health scores, evidence, and reproduction steps without applying any fixes.

Core Features & Use Cases

  • Report-only QA testing that documents defects with evidence such as screenshots, repro steps, and health scores.
  • Structured output suitable for triage, bug bash, or sprint QA without modifying the codebase.
  • Use cases include regression verification, exploratory testing, and pre-release QA where changes must not be introduced.

Quick Start

Provide the target URL and run a report-only QA scan to generate a structured bug report.

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 structured bug report for a web application?

Run a report-only QA scan by providing the target URL to identify and document defects, outputting a structured bug report with health scores, repro steps, and screenshots for triage.

Can I run regression testing on a web app without modifying the codebase?

Use report-only QA testing to verify regressions and document defects with evidence like screenshots and health scores, ensuring changes are not introduced to the codebase during sprint QA.

What is report-only QA testing and when do I need it?

Report-only QA testing identifies and documents web app defects with health scores and evidence without applying fixes, needed during bug bash sessions, regression testing, and pre-release QA cycles.

Does this bug reporting approach include reproduction steps and screenshots?

Yes, the structured bug report outputs reproduction steps and screenshots as evidence alongside a health score, providing clear documentation for triage during sprint QA and bug bash sessions.

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

Report-only QA strictly identifies and documents defects without applying fixes, meaning developers must implement codebase changes separately to resolve the issues found during the bug bash or regression scan.