qa-only

Generate structured QA reports with health scores and reproducible steps for web applications.

11|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/KSD-CO/IronCode --skill qa-only-ksd-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/KSD-CO/IronCode/tree/main/packages/ironcode/skills/qa-only
Command: npx skills add https://github.com/KSD-CO/IronCode --skill qa-only-ksd-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing eliminates the noise of immediate fixes during QA by generating a structured report that includes a health score, screenshots, and reproducible steps for developers to address later.

Core Features & Use Cases

  • Systematic manual testing of web applications to produce evidence-rich QA reports
  • Health-score calculation and structured issue reproduction
  • Diff-aware mode on feature branches and full exploration mode for URLs

Quick Start

Invoke the skill with /qa-only <url> to start a report-only QA run against your web app.

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 screenshots and reproducible steps for a web application?

You can generate a structured QA report by running a non-destructive testing session against your web app, which automatically collects screenshots, calculates a health score, and documents reproducible steps for developers to review later.

Can I run report-only QA testing on a feature branch without applying code fixes?

Yes, report-only QA testing supports a diff-aware mode specifically for feature branches, allowing you to identify issues and document evidence without applying any code changes to your staging environment or application.

What is a health score in the context of web application QA reporting?

A health score is a calculated metric included in a structured QA report that summarizes the overall quality and stability of a web application based on the issues identified during a non-destructive testing session.

How do I document reproducible steps for manual testing on a staging environment?

By executing a report-only QA run on your staging environment, the testing process systematically captures evidence and generates concise, shareable documentation containing the exact reproducible steps needed to replicate identified issues.

What is the best way to perform non-destructive QA testing on a URL?

The best way to perform non-destructive QA testing on a URL is to use a full exploration mode that systematically traverses the application, collects automated evidence like screenshots, and outputs a structured report without altering the codebase.

Does report-only QA testing support automated evidence collection for feature branches?

Yes, report-only QA testing supports automated evidence collection through its diff-aware mode, which systematically identifies issues on feature branches and compiles them into shareable documentation with screenshots and health scores.