qa-only

Generate structured QA bug reports with health scores, screenshots, and repro steps.

Updated May 11, 2026
One-click install
npx skills add https://github.com/wodeh/gstack-kimi --skill qa-only-wodeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/wodeh/gstack-kimi/tree/main/qa-only
Command: npx skills add https://github.com/wodeh/gstack-kimi --skill qa-only-wodeh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify and report bugs in a web application without applying any fixes, delivering a structured QA report that includes a health score, screenshots, and reproducible steps.

Core Features & Use Cases

  • Systematic, report-only QA tests that produce a health score, screenshots, and clear repro steps without code changes.
  • Voice-triggered QA tasks (e.g., "bug report", "qa report only") for quick activation.
  • Use during maintenance, bug triage, and audits where visibility into issues is needed and a repeatable report is preferred over hard fixes.

Quick Start

Run the QA-only skill to generate a bug report for the current web application without applying any 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 bug report for a web application without changing the code?

Generate a bug report for a web application without code changes by running a plan-only QA process that outputs a structured report. It includes a health score, screenshots, and reproducible steps to provide visibility into issues during maintenance or audits.

What is a QA health score and how does it help with bug triage?

A QA health score is a metric in a structured bug report that quantifies a web application's overall condition. It assists bug triage by providing a repeatable visibility metric alongside detailed screenshots and reproducible steps.

Can I trigger a QA report only using voice commands?

Yes, you can trigger a QA report using voice commands like "bug report" or "qa report only" for quick activation. This initiates the plan-only testing workflow to identify issues and generate structured reports without applying fixes.

Does plan-only QA testing integrate with existing bug triage workflows?

Plan-only QA testing integrates with existing /qa processes to guide subsequent fixes. It delivers structured reports containing health scores and repro steps, fitting maintenance and bug triage scenarios where issue visibility is required.

Why use a report-only QA approach instead of applying fixes immediately?

Use a report-only QA approach when you need visibility into web application issues via a repeatable report rather than hard fixes. It suits audits and bug triage by generating structured documentation with health scores and repro steps before committing to code changes.