qa

Automate web application QA testing and record results across three tiers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically QA test a web application and fix bugs found. Runs QA testing, then iteratively fixes bugs in source code, committing each fix atomically and re-verifying. Use when asked to "qa", "QA", "test this site", "find bugs", "test and fix", or "fix what's broken".

Core Features & Use Cases

  • Automated QA testing across multiple tiers: Quick, Standard, Exhaustive.
  • Atomic commits for each fix with re-verification to ensure stability.
  • Proactive suggestions when features are ready for testing or review, plus ship-readiness summaries.

Quick Start

Run a full QA pass on the target web app and generate a health and ship-readiness report.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate testing and bug fixing for my web application?

Automated testing and bug fixing is handled by running structured QA passes on your web application, identifying issues, and iteratively fixing them in source code with atomic commits. It then re-verifies each fix to ensure application stability.

What is the best way to generate a ship-readiness report before a release?

To generate a ship-readiness report, run a full QA pass to evaluate your web application's health. The process outputs before and after health scores alongside fix evidence, providing a clear summary to guide your release decisions.

Can I choose different testing depths for quality assurance?

You can choose from three quality assurance testing depths: Quick, Standard, and Exhaustive. This allows you to balance testing thoroughness with execution time based on your current development phase and review needs.

How are source code bug fixes verified during automated testing?

Bug fixes are verified through an iterative process where each fix is committed atomically. After the source code is updated, the system re-verifies the web application to confirm the fix resolved the issue without introducing regressions.

Does automated QA testing work without external dependencies?

Automated QA testing operates without external dependencies, running directly within your environment. It systematically tests the web application, applies source code fixes, and generates health scores and ship-readiness summaries independently.