skills.rest
rkumar261
rkumar261COMMUNITY
Explore all skills by this author →
𝕏@r_kumar261GitHub

qa-only

Identify and document web application bugs with screenshots, console logs, and navigation paths.

1|Updated Dec 23, 2025
Search Tags:#automation#testing#qa#evidence#browser#repro#bug-report
One-click install
npx skills add https://github.com/rkumar261/studio-cast --skill qa-only-rkumar261
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/rkumar261/studio-cast/tree/main/.claude/skills/gstack/qa-only
Command: npx skills add https://github.com/rkumar261/studio-cast --skill qa-only-rkumar261

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Report-only QA testing that systematically identifies and documents bugs in a web application without applying any fixes, ensuring stakeholders receive objective, reproducible evidence.

Core Features & Use Cases

  • Systematic exploratory testing that captures screenshots, console logs, and navigation paths
  • Produces a structured bug report with evidence, steps, and a health assessment
  • Useful for audits, off-cycle QA passes, and test-plan validation without code changes

Quick Start

Run a browser-based QA pass on the target URL and generate a structured bug report.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I document web app bugs with reproducible evidence during exploratory testing?▼

You can document web app bugs by running a browser-based exploration that captures screenshots, console logs, and navigation paths to produce a structured bug report with clear reproduction steps.

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

Report-only QA testing is the process of systematically identifying and documenting application bugs without applying any code fixes, useful for audits, off-cycle QA passes, and test-plan validation.

Can I run automated QA passes on a web application without modifying the source code?▼

Yes, you can run automated QA passes that explore the target URL and capture objective evidence like console logs and screenshots, ensuring the source code remains completely unchanged.

How do I generate a structured bug report with screenshots and navigation paths?▼

To generate a structured bug report, perform browser-based exploration of the application to automatically capture screenshots, console logs, and navigation paths into a comprehensive health assessment.

What's the best way to capture console logs and screenshots for a strict QA workflow?▼

The best way to capture this evidence for strict QA workflows is using a systematic browser exploration process that records console logs and screenshots alongside a structured health assessment report.

What are the limitations of report-only QA testing for web applications?▼

The main limitation of report-only QA testing is that it strictly identifies and documents bugs with evidence but does not apply any fixes or modify the application code to resolve the issues found.

Related Skills

Explore More Software Engineering Skills→
aayushsoamaayushsoam
1

dogfood

Automate exploratory QA testing of web applications with browser automation and structured bug reports.

Community
Advanced
latestaiagentslatestaiagents
5

bug-reporting

Generates structured bug reports with reproduction steps and evidence templates for developers.

Official
Basic
matthew-johnsonmatthew-johnson

dogfood

Automate exploratory QA testing of web applications and generate structured bug reports.

Community
Intermediate
moogieonmoogieon

qa

Automate QA testing and iteratively fix bugs in web application source code.

Community
Advanced