qa-only

Generate structured QA health reports with screenshots and reproducible steps.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/SeaLion-hub/DICEE --skill qa-only-sealion-hub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/SeaLion-hub/DICEE/tree/main/.agents/skills/gstack/qa-only
Command: npx skills add https://github.com/SeaLion-hub/DICEE --skill qa-only-sealion-hub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates report-only QA testing to systematically identify issues in a web application and produce a structured report with evidence but never applying fixes.

Core Features & Use Cases

  • Structured QA reports with health scores, screenshots, and reproducible steps.
  • Supports both manual and automated testing workflows for bug triage and verification.
  • No-fix policy ensures changes are not made to the production codebase during testing; ideal for audit trails and release readiness.

Quick Start

Provide the target URL and run the QA workflow to generate the 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 QA report with reproducible steps for web application testing?

To generate a QA report for web application testing, you provide the target URL and run the workflow. It systematically identifies issues and produces a structured report with health scores, screenshots, and reproducible steps without applying code fixes.

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

Report-only QA testing is the process of evaluating a web application to identify issues and produce a structured health report with evidence, without applying fixes. You need it for bug triage, release readiness, and maintaining audit trails during testing workflows.

Can I use this QA testing workflow for both manual and automated bug triage?

Yes, you can use this QA testing workflow for both manual and automated bug triage. It operates across these testing scenarios to generate structured health reports with screenshots and reproducible steps for verification workflows.

Does this web application testing approach apply fixes to the production codebase?

No, this web application testing approach enforces a no-fix policy and never applies changes to the production codebase. It strictly generates a structured report with health scores, screenshots, and reproducible steps, making it ideal for audit trails.

What is the best way to capture screenshots and health scores during bug verification?

The best way to capture screenshots and health scores during bug verification is to use an automated report-only QA workflow. It generates a structured health report with visual evidence and reproducible steps without modifying the underlying application code.