skills.rest
cropsgg
cropsggCOMMUNITY
Explore all skills by this author →
GitHub

qa-report

Identify browser UI defects with reproducible steps and evidence.

15|5|Updated May 17, 2026
Search Tags:#ui#qa#reporting#evidence#browser#health-score#repro-steps
One-click install
npx skills add https://github.com/cropsgg/skills --skill qa-report-cropsgg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-report
Source: https://github.com/cropsgg/skills/tree/main/skills/engineering/qa-report
Command: npx skills add https://github.com/cropsgg/skills --skill qa-report-cropsgg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report-only browser QA with structured findings and repro steps — no code fixes.

Core Features & Use Cases

  • Manual exploration of UI flows with real user interactions
  • Evidence collection: screenshots, DOM state, and logs
  • Health score and severity-based findings reporting

Quick Start

Run the qa-report skill against the target URL to generate a structured QA findings report.

Frequently Asked Questions about qa-report

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

FAQPage Schema
How do I generate a structured QA report for browser UI defects?▼

You can generate a structured QA report by running the skill against a runnable URL in local, staging, or preview environments. It captures screenshots, logs DOM state, and outputs a Markdown report with severity levels and a health score.

What is a UI health score in pre-release QA reporting?▼

A UI health score in QA reporting is a summarized metric generated alongside severity-based findings to quantify browser UI stability. It provides a quick overview of defect severity during pre-release QA cycles.

Can I use browser QA reporting on staging and preview environments?▼

Browser QA reporting supports local, staging, and preview environments. It requires a headless or visible browser to interact with UI flows and capture evidence during pre-release QA cycles.

What evidence do I need to collect for reproducible UI defect findings?▼

Reproducible UI defect findings require collecting screenshots, DOM state logs, and interaction traces. The skill captures this evidence during manual UI flow exploration to ensure defects are accurately documented.

Does the structured QA report include code fixes for browser UI defects?▼

Structured QA reporting does not include code fixes for browser UI defects. It provides report-only findings with reproducible steps and evidence, deferring code modifications to developers.

Related Skills

Explore More Software Engineering Skills→
LamseyahEliasLamseyahElias

dogfood

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

Community
Advanced
L3DigitalNetL3DigitalNet
6

repo-manager-assessment

Orchestrate multi-module GitHub repository health assessments with severity-grouped findings.

Official
Advanced
SnakeOSnakeO
9

debug:angular

Diagnose Angular runtime errors using DevTools, ng.probe, and console utilities.

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