qa-only

Automate browser-based QA testing and export structured reports with evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams need a deterministic, repeatable way to test web apps and generate structured reports that document health, issues, and reproduction steps without performing code fixes.

Core Features & Use Cases

  • Manual trigger only: invoked by /qa-only to run curated QA sessions.
  • Report-only QA testing: produces health scores, screenshots, and repro steps for bugs without applying changes.
  • Evidence-rich workflow: collects console errors, navigation checks, and accessibility signals to guide future improvements.

Quick Start

Run /qa-only to start a browser-based QA pass on the current app and generate a comprehensive report in .adeel/qa-reports.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I automate manual QA testing for a web application?

Automate manual QA testing using browser-based exploration triggered by /qa-only to capture health scores, screenshots, console logs, and reproduction steps without requiring any code changes.

How do I generate a structured QA report with screenshots and reproduction steps?

Generate a structured QA report by running a browser-based exploration that collects screenshots, console errors, navigation checks, and repro steps, exporting the evidence-backed results to the .adeel/qa-reports directory.

Can I use browser automation to reproduce bugs without applying code fixes?

Browser automation performs report-only QA testing to reproduce bugs and document issues with evidence without applying any code changes to the web application.

What is the best way to run regression testing with evidence-backed console logs?

Regression testing uses browser automation to capture health scores, console logs, and accessibility signals, producing a repeatable, evidence-backed report for future improvements.

Does QA testing with browser automation require modifying my web app's source code?

Browser-based QA testing requires no code changes, leveraging browser automation to perform manual review, regression testing, and bug reproduction directly on the current application.

Why should I use automated browser exploration instead of manual review for QA?

Automated browser exploration provides a deterministic, repeatable way to test web apps and document health, issues, and reproduction steps, replacing inconsistent manual review with structured evidence.