qa-only

Identify web application issues and generate a structured Markdown QA report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing identifies UI and interaction issues in web applications without making code changes, delivering a structured, shareable bug report for stakeholders.

Core Features & Use Cases

  • Systematically explores user flows, captures evidence (screenshots and console logs), and documents reproducible steps for each issue.
  • Generates a health score and a concise Top 3 list of fixes without modifying source code.
  • Useful when you need a bug report, not a fix, such as handoffs to developers or QA governance.

Quick Start

Run the QA tool with /qa-only against your target URL to generate a report-only test without fixes.

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 for a web app without modifying source code?

Report-only QA testing analyzes a target URL to identify UI and interaction issues. It navigates pages, captures screenshots and console logs, and outputs a structured Markdown bug report with reproducible steps without suggesting code fixes.

What is included in a structured web application bug report?

A structured bug report includes a health score, a Top 3 list of findings, captured screenshots and console logs, and documented reproducible steps for each identified issue to facilitate developer handoffs.

How do I test user flows and capture console errors against a dev server?

You can test user flows against a dev server by running the QA tool against your target URL. It systematically explores interactions, captures console errors as evidence, and documents the findings in a Markdown report.

Can I use this QA testing approach for developer handoffs and governance?

Yes, report-only QA testing is designed for handoffs and QA governance. It produces a shareable bug report with evidence and reproducible steps, ensuring developers receive clear issues without automated code changes.

Does report-only QA testing suggest fixes or changes to my web application?

No, report-only QA testing does not apply fixes or suggest code changes. It exclusively identifies and documents issues, providing a health score and top findings to help stakeholders prioritize fixes separately.

What's the best way to document UI bugs with screenshots for stakeholders?

The best way to document UI bugs for stakeholders is generating a report that pairs reproducible steps with visual evidence like screenshots and console logs, alongside a concise health score to summarize application stability.