qa-only

Generate a QA health report with score, screenshots, and repro steps.

8|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill qa-only-shaheerkhawaja
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/skills/qa-only
Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill qa-only-shaheerkhawaja

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only QA testing eliminates the need to modify code to verify quality; it generates a structured health report with scoring, screenshots, and reproducible steps so teams can assess a codebase without making changes.

Core Features & Use Cases

  • Generate a health-score report for a codebase without applying fixes.
  • Capture screenshots and document reproducible steps for issues.
  • Use cases include quick audits, compliance checks, and stakeholder communication.

Quick Start

Run qa-only on your repository to generate the health 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 a QA health report for a codebase without modifying the code?

Read-only QA testing generates a health report with a score, screenshots, and reproducible steps without applying code changes, allowing teams to assess a codebase safely. It is useful for quick audits, compliance checks, and stakeholder communication.

Can I perform a quick QA audit of my repository without applying code fixes?

Read-only QA testing generates a health report with a score, screenshots, and reproducible steps without applying code changes, allowing teams to assess a codebase safely. It is useful for quick audits, compliance checks, and stakeholder communication.

Does read-only QA testing capture screenshots and document repro steps for bugs?

Read-only QA testing generates a health report with a score, screenshots, and reproducible steps without applying code changes, allowing teams to assess a codebase safely. It is useful for quick audits, compliance checks, and stakeholder communication.

What is the best way to verify codebase quality for stakeholder communication without changing code?

Read-only QA testing generates a health report with a score, screenshots, and reproducible steps without applying code changes, allowing teams to assess a codebase safely. It is useful for quick audits, compliance checks, and stakeholder communication.

Do I need write access to the target codebase to run accessibility checks and generate a health score?

Read-only QA testing generates a health report with a score, screenshots, and reproducible steps without applying code changes, allowing teams to assess a codebase safely. It is useful for quick audits, compliance checks, and stakeholder communication.