qa-only

Automate browser-based QA testing and generate structured health reports with screenshots.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/lendtrain/complete-pipeline --skill qa-only-lendtrain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/lendtrain/complete-pipeline/tree/main/skills/qa-only
Command: npx skills add https://github.com/lendtrain/complete-pipeline --skill qa-only-lendtrain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing helps teams identify bugs and issues without introducing fixes, delivering a structured health report with evidence and reproducible steps.

Core Features & Use Cases

  • Systematically test web applications and generate a consolidated QA report with health score, screenshots, and repro steps.
  • Support diff-aware testing on feature branches and full-site verification to catch regressions.
  • Telemetry and session logging to track QA activity and provide audit trails.

Quick Start

Run a browser-based QA pass by invoking the /qa skill for the current repository.

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 and generate a report without modifying my codebase?

Automated QA testing generates a structured health report with reproducible steps and screenshot evidence while preserving the codebase. It runs browser-based tests to document issues without applying fixes, supporting both quick smoke tests and full regression evaluations.

What is diff-aware QA testing for feature branches?

Diff-aware QA testing targets specific development branches to catch regressions by evaluating only the changed code paths. It produces a consolidated health report with console error collection and screenshot evidence, ensuring new changes do not introduce bugs.

How do I run a quick smoke test for web application verification?

Quick smoke test mode executes a rapid browser-based QA pass to verify core web application functionality. It outputs a structured health report with screenshots and session logging telemetry, providing an audit trail without modifying the repository.

Can I collect browser console errors during automated web testing?

Automated web testing supports interactive browser testing with comprehensive console error collection. It captures JavaScript errors during execution and includes them in a structured QA report with screenshots and reproducible steps for documented issue tracking.

Does report-only QA testing apply fixes to the codebase?

Report-only QA testing strictly documents issues without applying fixes to the codebase. It generates a health report with screenshots, reproducible steps, and telemetry logs to identify bugs, leaving the resolution to the development team.

What are the limitations of report-only QA testing?

Report-only QA testing is limited to documenting issues and does not apply code fixes or patches. It focuses on generating health reports, screenshots, and reproducible steps, requiring developers to manually address the identified bugs.