qa-only

Automate non-fixing QA testing of web applications and generate structured health reports with screenshots and reproducible steps.

4|1|Updated Sep 13, 2023
One-click install
npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill qa-only-louisfghbvc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/louisfghbvc/mcp-leetcode-crawler/tree/main/.agent/skills/qa-only
Command: npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill qa-only-louisfghbvc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically tests a web application and generates a structured bug-report style output containing health scores, evidence (screenshots), and reproducible steps, while intentionally not performing any fixes.

Core Features & Use Cases

  • Non-intrusive QA: runs comprehensive checks and returns a detailed report suitable for triage.
  • Evidence-rich output: health scores, screenshots, and precise repro steps to reproduce issues.
  • Reusable in CI/CD pipelines and manual testing contexts for quick handoffs.

Quick Start

Run the QA-only workflow against the current app to produce a structured, non-fixing report.

Frequently Asked Questions about qa-only

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate QA testing to generate bug reports with screenshots and repro steps?

Automated QA testing generates structured bug reports containing health scores, screenshots, and reproducible steps without altering application code, ensuring clear evidence collection for developer triage.

What is non-intrusive QA testing and when do I need it for web applications?

Non-intrusive QA testing runs comprehensive checks on web applications to surface issues and produce health reports without performing fixes, making it ideal for triage and stakeholder handoffs.

Can I integrate automated QA testing into a CI/CD pipeline?

Automated QA testing integrates directly into CI/CD pipelines and manual testing contexts, systematically testing web applications to produce structured reports with evidence and reproducible steps.

How do I get reproducible steps and evidence for bug reports during web testing?

Web testing produces evidence-rich output including health scores, screenshots, and precise reproducible steps to reproduce issues, ensuring developers have clear handoff documentation for triage.

Does report-only QA testing modify my codebase or application configuration?

Report-only QA testing intentionally does not perform any fixes or alter code, running comprehensive non-intrusive checks to return a detailed structured report suitable for triage.

What is the best way to surface web application issues for developer triage?

Surfacing web application issues for developer triage is best achieved through non-intrusive QA testing that produces evidence-rich health reports with screenshots and precise reproducible steps.