qa

Test web applications, fix bugs iteratively, and commit changes atomically.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/cattboy/lil_bro --skill qa-cattboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/cattboy/lil_bro/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/cattboy/lil_bro --skill qa-cattboy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and templates (resource) components.

What problem does it solve?

QA testing is essential to ship reliable software. This skill systematically tests a web application, identifies bugs, and guides fixes that are committed atomically and re-verified.

Core Features & Use Cases

  • End-to-end QA routines that catch regressions across features and flows.
  • Produces before/after health scores, fixes evidence, and ship-readiness summaries.
  • Uses a repeatable, atomic-fix cycle: test, fix, verify, commit, re-run.

Quick Start

Ask me to run QA on your site, e.g., "qa test this site", and I will test, fix, commit, and re-verify.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I run QA testing on a web application to prevent regressions?

Run QA testing by executing end-to-end routines on your web application to catch regressions across features. The process enforces a structured workflow with atomic fixes, measuring health scores and verifying ship-readiness before release.

What's the best way to automate bug fixes and ensure release readiness?

Automate bug fixes using a repeatable cycle of test, fix, verify, and commit. This approach ensures release readiness by producing before/after health scores, fix evidence, and ship-readiness summaries across your product features.

How does systematic QA testing produce health scores and fix evidence?

Systematic QA testing produces health scores by validating new features and flows, then generating before/after evidence. It uses an atomic-fix cycle where each bug fix is committed individually and re-verified to ensure measurable product health.

Can I use this QA workflow to validate new features before shipping?

Yes, you can use this QA workflow to validate new features before shipping. It is specifically applicable for preventing regressions and ensuring release readiness across the product through structured testing and iterative bug fixes.

Do I need any dependencies to run end-to-end QA routines?

No dependencies are required to run end-to-end QA routines. The skill operates independently to test your web application, identify bugs, and guide atomic commits using built-in references and templates.

Why does my web app need atomic commits during the bug fix cycle?

Atomic commits during the bug fix cycle isolate each fix for independent verification. This prevents overlapping changes from masking regressions, ensuring every bug fix is re-verified and contributes to an accurate ship-readiness summary.