gstack-qa-only

Tests web applications and generates structured QA reports with health scores, screenshots, and repro steps.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill gstack-qa-only-tayiorbeii
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-qa-only
Source: https://github.com/tayiorbeii/paperclip-factory-kit-hermes/tree/main/skills/paperclip/gstack-qa-only
Command: npx skills add https://github.com/tayiorbeii/paperclip-factory-kit-hermes --skill gstack-qa-only-tayiorbeii

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often need a clear picture of what is broken in a web application without anyone touching the code yet. This Skill systematically tests a web app and produces a structured, report-only QA document with a health score, screenshots, and reproduction steps, while guaranteeing no fixes or code changes are made. ## Core Features & Use Cases - Report-Only Testing: Systematically exercises a web application and records bugs without modifying any source code. - Structured QA Report: Produces a health score, annotated screenshots, and step-by-step reproduction instructions for each issue found. - Decision-Gated Workflow: Uses structured AskUserQuestion decision briefs so the user controls scope, and supports plan-mode and spawned-session operation. - Use Case: Before a release, ask for a bug sweep of your staging site. You receive a prioritized report with screenshots and repro steps that engineers can triage, while the codebase stays untouched. ## Quick Start Ask the agent to run a report-only QA pass on your web app and produce a bug report with screenshots and repro steps without changing any code.

Frequently Asked Questions about gstack-qa-only

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

FAQPage Schema
How do I get a QA bug report without changing any code?▼

Invoke this skill with a request like "just report bugs" or "test but don't fix". It systematically tests the web application and outputs a structured report with a health score, screenshots, and repro steps, and never edits source files.

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

Report-only QA stops after documenting issues with evidence and repro steps. The full test-fix-verify loop (the /qa skill) continues into fixing and re-verifying each bug. Use report-only when you want triage input before committing engineering time.

What does the QA report include?▼

The report contains an overall health score for the application, screenshots capturing each issue, and step-by-step reproduction instructions so engineers can confirm and fix bugs without re-discovering them.

Can this skill run in plan mode or automated spawned sessions?▼

Yes. In plan mode the skill's workflow takes precedence and its first prompt acts as the plan-mode entry. In spawned sessions it skips interactive prompts, auto-chooses recommended options, and ends with a completion report.

What happens if the AskUserQuestion tool is unavailable?▼

The skill stops and reports BLOCKED — AskUserQuestion unavailable. It does not silently auto-decide or write decisions to a plan file, since interactive decision gates are core to its workflow.