skills.rest
Shmurdoc
ShmurdocCOMMUNITY
Explore all skills by this author →
GitHub

qa-only

Automates web app QA testing and generates structured bug reports with health scores and screenshots.

Updated May 27, 2026
Search Tags:#quality assurance#regression testing#bug reports#qa testing#web application testing#report-only#bug documentation
One-click install
npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill qa-only-shmurdoc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-qa-only
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill qa-only-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually testing web applications and documenting bugs is time-consuming, inconsistent, and often misses critical edge cases. This skill automates systematic QA testing to produce structured, actionable bug reports without making any code changes, saving your team hours of manual documentation work.

Core Features & Use Cases

  • Systematic Web App Testing: Automatically covers all user flows, edge cases, and common failure points in your web application during testing.
  • Structured Bug Reports: Generates shareable reports that include a numerical health score, annotated screenshots of bug occurrences, and clear step-by-step reproduction instructions for every issue found.
  • Use Case: If you need to document all bugs in a pre-release build without assigning immediate fixes, this skill produces a consistent, triage-ready report your engineering and product teams can review and prioritize.

Quick Start

Use the qa-only skill to test the staging version of your web application and generate a full bug report with health score and screenshots.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I generate bug reports for a web application without modifying the code?▼

To generate bug reports without modifying code, you can use report-only quality assurance testing to systematically identify defects. This process produces a structured, shareable record of issues with reproduction instructions and a numerical health score for triage.

What is the best way to automate regression testing documentation for pre-release builds?▼

Automating regression testing documentation for pre-release builds involves executing systematic web application testing to capture defects. It generates structured bug reports containing annotated screenshots and step-by-step reproduction instructions for every identified issue.

Can I use automated QA testing to get a health score for my staging environment?▼

Yes, automated QA testing can evaluate your staging environment and produce a numerical health score. It systematically tests user flows and edge cases to document bugs, providing a clear record of application stability without applying immediate fixes.

Does report-only quality assurance testing provide step-by-step bug reproduction instructions?▼

Report-only quality assurance testing does provide step-by-step bug reproduction instructions for every identified defect. It systematically checks web applications and outputs structured bug documentation, including annotated screenshots of each bug occurrence for team review.

When should I use report-only QA testing instead of automated bug fixing?▼

You should use report-only QA testing instead of automated bug fixing when stakeholders need a clear, shareable record of issues for triage without immediate code changes. It is ideal for pre-release testing and bug triage workflows where engineering teams prioritize fixes later.

What is included in a structured bug report for web application testing?▼

A structured bug report for web application testing includes a numerical health score, annotated screenshots of bug occurrences, and step-by-step reproduction instructions. This triage-ready documentation helps engineering and product teams review and prioritize defects.

Related Skills

Explore More Software Engineering Skills→
guccangguccang
3

dogfood

Identify and document web application bugs through exploratory QA testing.

Community
Advanced
josephblaisjosephblais

github-analytics-scoring

Calculate GitHub repository health, issue, and pull request priority scores.

Community
Advanced
jaisonerickjaisonerick

fix-bugs

Reproduce QA-reported failures with failing tests and apply minimal code fixes.

Community
Advanced
DIGI-UWDIGI-UW

openelis-test-catalog-qa

Automate browser-based QA testing for OpenELIS Global with Playwright and generate pass/fail reports.

Official
Advanced