gstack-qa-only

Generate report-only QA results with health score, screenshots, and repro steps.

Updated May 19, 2026

Search Tags:#screenshots #qa #bug report #health score #web application testing #report-only #repro steps

Ready to run

npx skills add https://github.com/anilveersingh1308/copilot-skills --skill gstack-qa-only-anilveersingh1308

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gstack-qa-only
Source: https://github.com/anilveersingh1308/copilot-skills/tree/main/.github/skills/gstack-qa-only
Command: npx skills add https://github.com/anilveersingh1308/copilot-skills --skill gstack-qa-only-anilveersingh1308

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you produce a structured QA report that captures app health, screenshots, and precise repro steps, without making any code changes or claiming to fix issues.

Core Features & Use Cases

Report-only QA testing: Runs systematic checks and produces a structured health score, screenshots, and reproduction steps.
Bug-report style output: Optimized for requests like “just report bugs” or “test but don’t fix,” including proactive guidance when the user wants a report rather than code changes.
For the full loop, route to /qa: Keeps “no-fix” separation clear so you do not accidentally enter a fix-and-verify workflow.

Quick Start

Ask for a report-only QA run by saying: "qa report only for the web app and include a health score, screenshots, and step-by-step repro steps, but do not fix anything."

Frequently Asked Questions about gstack-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 applying code fixes?▼

To generate a bug report without code fixes, you can request a report-only QA run that produces a structured deliverable with health scores, screenshots, and step-by-step reproduction data while strictly avoiding any modifications to the application code.

What is report-only QA testing and when do I need it?▼

Report-only QA testing is the process of running systematic checks on a web application to capture its health score and reproduction steps without implementing fixes. It is needed for bug triage and validation scenarios where you require confirmation and evidence rather than code changes.

Can I get a health score and screenshots for bug triage without modifying the codebase?▼

Yes, you can get a health score and screenshots for bug triage without modifying the codebase by requesting a deterministic, report-only QA execution that focuses on health assessment and visual evidence capture while preventing any code alterations.

What is the best way to document step-by-step reproduction steps for web application testing?▼

The best way to document step-by-step reproduction steps is to use a report-only QA workflow that systematically captures precise repro data and screenshots in a structured bug-report format, ensuring clear validation evidence without attempting to fix the underlying issues.

How does report-only QA differ from a full fix-and-verify testing workflow?▼

Report-only QA differs from a full fix-and-verify workflow by strictly separating bug documentation from code changes. It focuses on generating health scores, screenshots, and repro steps, whereas a full workflow routes to a fix-and-verify process that modifies the application.

When should I not use a report-only approach for web application testing?▼

You should not use a report-only approach when you need automated code fixes or a fix-and-verify testing loop. This method is constrained to bug triage, health assessment, and evidence collection, intentionally avoiding any code modifications or issue resolutions.