skills.rest
himes19
himes19COMMUNITY
Explore all skills by this author →
GitHub

qa-only

Generate a read-only QA report documenting issues without code changes.

Updated Apr 12, 2026
Search Tags:#qa#reporting#quality-assurance#code-review#read-only#bug-documentation#test-process
One-click install
npx skills add https://github.com/himes19/pulsevolt-infra --skill qa-only-himes19
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/himes19/pulsevolt-infra/tree/main/skills/gstack/qa-only
Command: npx skills add https://github.com/himes19/pulsevolt-infra --skill qa-only-himes19

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Same QA methodology as the qa skill but report-only — no code changes. Use when you want a pure bug report without fixes, or when reviewing someone else's work.

Core Features & Use Cases

  • Report-only QA: Follow the same QA Phases 1-4 but generate a report without applying fixes.
  • Structured outputs: Produces a QA REPORT (READ-ONLY) with URL, tier, pages tested, issues, health score.
  • Peer review & audits: Ideal for third-party reviews or pre-fix evaluations without modifying code.

Quick Start

Run the qa-only workflow on a target page to generate a read-only QA 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 without modifying the code?▼

Generate a read-only QA report by running the qa-only workflow on a target web application page, which documents issues across QA phases 1-4 without applying fixes.

What is a read-only quality assurance report used for?▼

A read-only quality assurance report is used for peer reviews, audits, and bug triage to document issues and health scores without modifying code during pre-fix evaluations.

Can I use this QA workflow to review someone else's web application?▼

Yes, you can use this read-only QA workflow to review a third-party web application, as it outputs a structured bug report without making any code changes.

What is the best way to document bugs for a structured triage process?▼

The best way to document bugs for a structured triage process is to generate a QA report containing the URL, tier, pages tested, issues, and health score.

Does the report-only QA process include code fixes?▼

No, the report-only QA process explicitly excludes code fixes, following phases 1-4 of the QA workflow and stopping before the fix phase to output only a read-only report.

Related Skills

Explore More Software Engineering Skills→
studyzystudyzy

qa

Test web applications across three tiers and fix bugs with atomic commits.

Community
Advanced
yckkkkyckkkk
1

qa-only

Run report-only QA tests and generate a structured health report with screenshots.

Community
Intermediate
yocxy2yocxy2

qa-only

Test web applications and generate structured bug reports with health scores.

Community
Intermediate
Objective-ArtsObjective-Arts

qodana-scan

Run read-only Qodana static analysis to detect code issues.

Official
Intermediate