skills.rest
jeisenback
jeisenbackCOMMUNITY
Explore all skills by this author →
GitHub

qa-only

Identify and report web application issues with reproducible steps and screenshots.

Updated Mar 22, 2026
Search Tags:#testing#qa#reporting#evidence#web-app#bug-report#manual-testing
One-click install
npx skills add https://github.com/jeisenback/original-curse-killer --skill qa-only-jeisenback
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/jeisenback/original-curse-killer/tree/main/.claude/skills/qa-only
Command: npx skills add https://github.com/jeisenback/original-curse-killer --skill qa-only-jeisenback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams often need to observe an application without making changes and produce formal, evidence-backed reports. This Skill enforces a no-fix policy and focuses on finding and documenting issues instead.

Core Features & Use Cases

  • Non-invasive testing: Explore the app manually, capture findings with reproducible steps, and assemble a structured report.
  • Evidence-driven reporting: Attach screenshots and logs to issues; no code changes are made.
  • Use Case: A tester wants to report a UI misalignment or a broken form without attempting fixes, ensuring stakeholders receive a complete bug dossier.

Quick Start

Launch the qa-only workflow in your browser, explore the application, and generate a structured bug report with evidence.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I generate a structured bug report with reproducible steps for a web application?▼

A structured bug report enforces a no-fix policy during manual exploratory testing, capturing reproducible steps, UI misalignments, broken forms, and evidence like screenshots to provide stakeholders with a complete issue dossier.

Can I perform manual exploratory testing without altering production code?▼

Yes, non-invasive manual exploratory testing allows you to observe a web application without altering production code, focusing strictly on identifying issues and documenting findings rather than implementing fixes.

What is evidence-driven QA reporting and when do I need it?▼

Evidence-driven QA reporting documents issues by attaching screenshots and logs to reproducible steps. You need it when formal, evidence-backed bug documentation is required for stakeholder review without implementing fixes.

Does this approach work for testing small UI components as well as full web platforms?▼

Yes, this manual exploratory testing approach applies to any web application scale, from small UI components to full platforms, ensuring consistent evidence-rich reporting and structured issue documentation.

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

The primary limitation of report-only QA testing is its strict no-fix policy; it identifies and documents issues with evidence but does not implement code changes or resolve the underlying bugs.

Related Skills

Explore More Software Engineering Skills→
XyHalcyonXyHalcyon

dogfood

Automate exploratory QA testing of web applications with structured bug reporting.

Community
Advanced
lachiehlachieh

qa-only

Automate web app QA testing and generate evidence-rich bug reports.

Community
Intermediate
yocxy2yocxy2

qa-only

Test web applications and generate structured bug reports with health scores.

Community
Intermediate
mr-daedaliummr-daedalium
107

qa-only

Generate a report-only QA health score with evidence screenshots and reproducible steps.

Community
Intermediate