skills.rest
JovieInc
JovieIncOFFICIAL
Explore all skills by this author →
WebsiteGitHub

qa-only

Identify and report QA findings for a web application without applying fixes.

Updated Aug 2, 2025
Search Tags:#testing#screenshots#qa#reporting#web-app#bug-report#repro-steps
One-click install
npx skills add https://github.com/JovieInc/Jovie --skill qa-only-jovieinc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/JovieInc/Jovie/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/JovieInc/Jovie --skill qa-only-jovieinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing to document issues without applying fixes, preserving the original codebase for audit, compliance, and knowledge transfer.

Core Features & Use Cases

  • Structured bug reports with screenshots, steps to reproduce, and console logs.
  • Non-destructive testing: no code changes or deployments; ideal for audits and documentation of issues.
  • Diff-aware and URL-driven testing modes to cover feature branches and live QA runs.

Quick Start

Run a report-only QA pass against your target URL using the /qa workflow.

Frequently Asked Questions about qa-only

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run QA testing on a web app without changing the codebase?▼

You can run non-destructive QA testing to identify and document issues without modifying the codebase, preserving the original state for audits and compliance. The skill outputs structured bug reports with screenshots, console logs, and repro steps.

What is non-destructive QA reporting and when do I need it?▼

Non-destructive QA reporting documents web application bugs without modifying code or triggering deployments. It is needed for audit, compliance, and knowledge transfer where preserving the original codebase state is mandatory.

Can I test feature branches using URL-driven QA reports?▼

Yes, URL-driven testing modes support verifying feature branches and live QA runs. You can systematically check UI behavior and generate structured bug reports with console logs and screenshots by targeting a specific URL.

How do I generate structured bug reports with screenshots and repro steps?▼

You generate structured bug reports by running a report-only QA pass against your target URL via the defined workflow. It captures screenshots, console logs, and repro steps into a report template for cross-session traceability.

Does QA reporting require authentication for testing live web apps?▼

Authentication is required if the target web application needs it. You must provide access to the target URL and necessary credentials to systematically verify UI behavior and catch regressions.

Where are QA report files stored for cross-session traceability?▼

QA report files are written to the .gstack/qa-reports directory using a report template. This ensures cross-session traceability for your web application testing evidence.

Related Skills

Explore More Software Engineering Skills→
cegit27cegit27
3

qa-only

Generate structured QA bug reports with health scores and reproduction steps.

Official
Intermediate
ekrishguptaekrishgupta
1

qa-only

Automate browser-based QA testing and generate structured reports with screenshots and repro steps.

Community
Advanced
ulpi-ioulpi-io
13

browse-qa

Convert QA targets into executable browse scenarios and regression flows.

Official
Advanced
uzumaki-incuzumaki-inc

qa-only

Generate a report-only web-app QA health report with score, screenshots, and reproduction steps.

Official
Advanced