qa

Test web applications, fix bugs, and commit changes with verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill systematically tests web applications, identifies bugs, and automatically fixes them in the source code, ensuring a higher quality release.

Core Features & Use Cases

  • Automated Testing: Performs comprehensive QA testing across different tiers (Quick, Standard, Exhaustive).
  • Bug Fixing: Iteratively fixes identified bugs directly in the codebase with atomic commits.
  • Verification: Re-tests fixes and provides before/after evidence, including screenshots and health scores.
  • Use Case: A developer has just pushed a new feature to a branch and wants to ensure it's bug-free before merging. They can run this Skill to test the changes, fix any regressions, and get a ship-readiness summary.

Quick Start

Use the qa skill to test the application at http://localhost:3000 and fix any critical or high-severity bugs found.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automatically test a web application and fix bugs in the source code?

Automated QA testing systematically tests a web application, identifies bugs, and iteratively fixes them directly in the source code with atomic commits. It then re-verifies the fixes and provides before/after health scores to ensure the application is ship-ready.

What's the best way to run regression testing after pushing a new feature to a branch?

Regression testing after pushing a new feature uses diff-aware modes to identify regressions. It automatically fixes broken functionality, commits changes atomically, and generates a ship-readiness summary with before/after health scores before merging.

Do I need git and a browse binary to run automated QA testing?

Yes, automated QA testing requires a browse binary for web application interaction and git for source code management. These dependencies are necessary to navigate the application, identify bugs, and iteratively apply atomic commits to fix them.

How does bug fixing verification work when testing a web app?

Bug fixing verification works by re-testing applied fixes and capturing before/after evidence, including screenshots and health scores. This iterative process ensures source code changes successfully resolve identified bugs before producing a ship-readiness summary.

What testing tiers are available for web application QA automation?

Web application QA automation supports Quick, Standard, and Exhaustive testing tiers. These tiers allow developers to control the depth of testing, from rapid checks to comprehensive validation, when identifying bugs and generating before/after health scores.

Why does my web application QA automation produce a ship-readiness summary?

A ship-readiness summary is produced to aggregate automated QA testing and bug fixing results. It provides developers with final health scores and fix evidence, indicating whether the web application is stable enough for release.