qa-only

Generate structured QA bug reports with evidence from browser testing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables testers to generate structured QA bug reports for web applications without making any code fixes, ensuring consistent documentation and faster handoffs.

Core Features & Use Cases

  • Structured reporting: Produce reproducible bug reports with evidence such as screenshots, console logs, and navigational steps.
  • Non-intrusive: Performs tests as a user and never applies fixes or edits code.
  • Workflow guidance: Provides a repeatable QA workflow from setup to report wrap-up, suitable for team handoffs.

Quick Start

Describe the target site and run the QA workflow to generate a structured 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 structured bug reports for web app testing without modifying code?

You can generate structured bug reports for web app testing without modifying code by running an automated browser-based QA workflow. This approach performs tests as a user and produces stakeholder-ready reports with reproducible steps, console logs, and screenshots.

What evidence does automated QA reporting include for end-to-end web application testing?

Automated QA reporting includes evidence such as screenshots, console logs, and navigational steps for end-to-end web application testing. Every bug report enforces reproducible steps and collects evidence to ensure consistent documentation and faster team handoffs.

Can I use automated QA testing for web apps if I don't want any code fixes applied?

Yes, you can use this non-intrusive automated QA testing approach if you don't want any code fixes applied. It operates strictly as a reporting tool that identifies issues and redacts sensitive data without editing code or applying fixes to the web application.

What is the best way to ensure reproducible steps in QA bug reports for web applications?

The best way to ensure reproducible steps in QA bug reports is to follow a repeatable workflow from setup to report wrap-up. This automated process enforces evidence collection and structured documentation for every finding across the end-to-end testing workflow.

Does automated browser-based QA reporting redact sensitive data in bug reports?

Automated browser-based QA reporting does redact sensitive data in bug reports. It ensures that all evidence, including screenshots and console logs collected during the web application testing workflow, is sanitized for safe stakeholder handoffs.