qa

Test web applications in a browser, fix discovered bugs, and commit verified fixes atomically.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/westkite1201/garden-engine --skill qa-westkite1201
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/westkite1201/garden-engine/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/westkite1201/garden-engine --skill qa-westkite1201

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually clicking through a web app to find bugs is slow and easy to skip before shipping. This Skill systematically QA tests a web application like a real user, then fixes the bugs it finds in source code with atomic commits and re-verifies each fix. ## Core Features & Use Cases - Test → Fix → Verify loop: Explores pages, clicks every interactive element, checks console errors, then fixes found bugs with one commit per fix and re-tests. - Diff-aware mode: On a feature branch with no URL, it analyzes the branch diff, identifies affected pages/routes, and scopes testing to what changed. - Tiered severity: Quick (critical/high), Standard (+ medium), or Exhaustive (+ cosmetic) tiers control which issues get fixed, with before/after health scores and a ship-readiness report. - Test framework bootstrap: Detects missing test infrastructure, installs an appropriate framework, writes regression tests, and sets up CI. - Use Case: You just finished a feature branch and ask "qa this" — it detects your local dev server, tests the pages your branch touched, fixes a broken form validation, commits the fix, and produces a report with before/after screenshots. ## Quick Start Ask the AI to QA test the current feature branch and fix any bugs it finds, or provide a URL such as http://localhost:3000 to test a running app.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I QA test my web app automatically before shipping?

Run the qa skill with a target URL or on a feature branch. It navigates pages, clicks interactive elements, checks console errors, fixes found bugs with atomic commits, and produces a report with before/after health scores and ship-readiness summary.

How does diff-aware QA testing work on a feature branch?

When invoked without a URL on a feature branch, it analyzes the branch diff to identify affected pages and routes, detects a running local dev server on common ports, and scopes browser testing to the changed functionality while checking for regressions.

What is the difference between Quick, Standard, and Exhaustive QA tiers?

Tiers control which severity issues get fixed. Quick fixes critical and high severity only, Standard adds medium severity, and Exhaustive also fixes low and cosmetic issues. Standard is the default tier.

Can it set up a test framework if my project has none?

Yes. It detects the project runtime, researches current best practices, asks you to choose a framework, installs and configures it, writes initial real tests, adds a CI workflow, and documents conventions in TESTING.md.

Why does the QA skill require a clean git working tree?

Each bug fix gets its own atomic commit, so uncommitted changes would mix with fix commits. If the tree is dirty, it asks you to commit or stash your changes before starting the QA run.

Does it support regression testing against previous QA runs?

Yes. Regression mode compares the current run against a saved baseline report, showing health score deltas, issues fixed since baseline, and new issues introduced since the baseline was captured.