qa-only

Run report-only QA tests on a web application and generate a structured health report with screenshots and repro steps.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill qa-only-jonkiky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/jonkiky/ccdi-federation-ai/tree/main/.agents/qa-only
Command: npx skills add https://github.com/jonkiky/ccdi-federation-ai --skill qa-only-jonkiky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing of a web application that produces a structured health report with screenshots and repro steps, while never applying fixes.

Core Features & Use Cases

  • Systematically tests a web application and generates a structured health report with a health score, screenshots, and repro steps.
  • Use when you want a bug report without code changes; for a full test-fix-verify loop, use /qa.

Quick Start

Request a bug-only QA report by telling me to run qa-only 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 run a QA audit on a web app without changing any code?

Run a report-only QA audit to systematically test your web app and generate a structured health report with screenshots and repro steps, without applying any code fixes.

What is the difference between report-only QA and a full test-fix-verify loop?

Report-only QA detects issues, summarizes health, and provides actionable repro steps for developers without touching code, whereas a full test-fix-verify loop applies and verifies code changes.

Can I get a bug report with screenshots and repro steps for my web application?

Yes, you can request a bug-only QA report to systematically test your web application and produce a structured health report containing a health score, screenshots, and repro steps.

How do I perform an ad-hoc regression check to find bugs in my web app?

Initiate an ad-hoc bug-hunting session through a report-only QA test to identify issues and output a structured health report with detailed repro steps for your developers.

When should I use a report-only QA approach instead of automated fixing?

Use a report-only QA approach when you need a quick ad-hoc audit, regression check, or bug-hunting session to detect issues and document repro steps without modifying your application code.