qa-only

Run report-only QA tests on web applications with browser interactions and health scoring.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Teams often need a fast, objective assessment of a web application’s health without making any code changes. This skill provides a thorough, report‑only QA run that surfaces bugs, regressions, and performance issues while leaving the code untouched.

Core Features & Use Cases

  • Automated browser exploration: Navigates pages, interacts with forms, and captures console errors and screenshots.
  • Health scoring & regression: Calculates a weighted health score and can compare against a previous baseline.
  • Flexible modes: Supports full, quick, diff‑aware, and regression testing, with optional authentication handling.

Quick Start

Run /qa-only on your web app’s URL to receive a structured bug report with screenshots and a health score.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I run automated web testing without modifying my codebase?

You can run report-only QA testing by executing the skill on your web app's URL, which systematically navigates pages, captures screenshots, logs console errors, and calculates a health score without touching your code.

What is a web application health score and how does regression testing use it?

A web application health score is a weighted metric calculated during a QA test. Regression testing uses this score to compare current results against a previous baseline to identify new bugs or performance issues.

Do I need authentication details to perform browser exploration on a private web app?

Authentication details are optional for browser exploration. You can provide them to allow the QA test to conduct full-page exploration behind login screens, but they are not strictly required if the URL is public.

What's the best way to capture console errors and screenshots during a QA test?

The best way to capture console errors and screenshots is using an automated browser exploration tool that visits the target URL, interacts with forms, and systematically records outputs for your bug documentation.

Can I use diff-aware testing to compare a web app against a previous baseline?

Yes, you can use diff-aware and regression testing modes to compare the current state of your web application against a previous baseline, surfacing visual or functional regressions without changing code.

What dependencies are required to execute a report-only QA test?

To execute a report-only QA test, you need a functional browse binary and a reachable URL. Optional authentication details can be provided to access protected areas for full-page exploration.