qa-only

Test web applications and generate structured bug reports without modifying the codebase.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/smarmen86/claude-code-kit --skill qa-only-smarmen86
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/smarmen86/claude-code-kit/tree/main/skills/qa-only
Command: npx skills add https://github.com/smarmen86/claude-code-kit --skill qa-only-smarmen86

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the need for structured, objective quality assurance reporting without triggering automated code fixes or refactoring, ensuring the AI remains in an observational role.

Core Features & Use Cases

  • Structured Reporting: Generates comprehensive bug reports including health scores, screenshots, and reproduction steps.
  • Non-Destructive Testing: Performs systematic web application testing while strictly avoiding any modification to the codebase.
  • Use Case: Use this when you need a professional QA audit of a staging environment to document issues for your development team without the AI attempting to patch the bugs itself.

Quick Start

Invoke the qa-only skill to perform a full bug report on the current web application.

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 for a web application without modifying the codebase?

You can generate a structured bug report by running non-destructive web application testing that collects health scores, reproduction steps, and visual evidence while strictly avoiding any code changes. This ensures the AI remains in an observational role for your QA workflow.

What is non-destructive quality assurance testing and when do I need it?

Non-destructive quality assurance testing is a systematic process that evaluates a web application to document issues without triggering automated code fixes or refactoring. You need it when you want to audit a staging environment and hand off bug reports to your development team.

Can I use this QA workflow to document reproduction steps and collect visual evidence for my development team?

Yes, this QA workflow performs systematic web application testing to generate professional bug reports containing objective health scores, detailed reproduction steps, and visual evidence. It satisfies the requirement for reporting-only bug analysis for development teams.

Does this bug reporting process attempt to patch or fix the bugs it discovers?

No, the bug reporting process does not attempt to patch or fix discovered bugs. It strictly avoids modifying the codebase, ensuring the testing remains non-destructive and the AI acts purely in an observational capacity to document issues.

What is the best way to perform a QA audit of a staging environment without triggering automated refactoring?

The best way is to invoke a reporting-only bug analysis skill that performs systematic web application testing. This approach generates comprehensive bug reports including health scores and reproduction steps while ensuring the AI remains in an observational role without applying code fixes.