qa

Name: qa
Availability: InStock
Author: nuurpro

Run QA testing and bug fixing cycles for web applications.

1|1|Updated Mar 28, 2026

Search Tags:#automation #testing #qa #verification #bug-fix #health-score

Ready to run

npx skills add https://github.com/nuurpro/Converza_ai --skill qa-nuurpro

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/nuurpro/Converza_ai/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/nuurpro/Converza_ai --skill qa-nuurpro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA testing and bug fixing automation for web applications helps teams find, reproduce, and verify fixes quickly.

Core Features & Use Cases

End-to-end QA testing that reproduces defects and verifies fixes across builds.
Produces before/after health scores, fix evidence, and ship-readiness summaries for stakeholders.
Use Case: When asked to "qa" or "test this site", run a structured QA cycle and report results.

Quick Start

Ask me to start QA by saying 'qa' and I will test the site, fix bugs, and report before/after health scores.

Frequently Asked Questions about qa

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

FAQPage Schema

How do I automate QA testing and bug fixing for a web application?▼

Automate QA testing by invoking a prompt like 'qa' or 'test this site' to run a structured cycle that finds, reproduces, and verifies fixes. The process runs end-to-end across Quick, Standard, and Exhaustive tiers, outputting before/after health scores and ship-readiness summaries.

What is a ship-readiness summary in web app QA verification?▼

A ship-readiness summary is a structured report generated after a QA testing cycle that verifies bug fixes across builds. It includes before/after health scores and fix evidence, providing stakeholders with deterministic proof that the application is ready for release.

Can I run a report-only mode without applying bug fixes during testing?▼

Yes, you can run a report-only mode by invoking the /qa-only command. This performs the QA testing cycle to identify and reproduce defects without applying fixes, allowing you to review testing results and health scores before committing to changes.

Does the automated QA cycle support atomic commits after each bug fix?▼

Yes, the automated QA cycle requires deterministic task execution and makes atomic commits after each bug fix. This ensures that every verified fix is isolated and tracked, providing clear fix evidence from the initial test to the final re-verification state.

What is the best way to verify bug fixes across multiple web app builds?▼

The best way to verify bug fixes across builds is to run an exhaustive QA testing tier that reproduces defects and verifies fixes end-to-end. This approach generates before/after health scores and fix evidence to confirm that previous issues are fully resolved.

What tools are allowed during automated web app QA and bug fixing?▼

Allowed tools for automated QA and bug fixing include Bash, Read, Write, Edit, Glob, Grep, WebSearch, and AskUserQuestion. These tools support file manipulation, code searching, and environment interaction to execute tests, apply fixes, and generate structured reports.