qa

Identify and fix web application bugs with structured QA testing and atomic commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA teams and developers spend excessive time manually testing web apps, finding regressions, and coordinating fixes. This skill provides a structured approach to test, fix, and verify changes end-to-end, reducing cycle time and increasing confidence before shipping.

Core Features & Use Cases

  • Systematic QA testing of a web application, with tiered coverage (Quick, Standard, Exhaustive).
  • Atomic commits of each fix followed by re-verification to maintain a clean history.
  • Generates before/after health scores and a ship-readiness summary to guide release decisions.
  • Suitable for feature branches, bug fixes, and regression validation across frontend and backend changes.

Quick Start

Run /qa in your repository to start a quick smoke QA pass against the active app.

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 and bug fixing by running structured test passes that identify bugs, apply atomic commits for each fix, and re-verify with automated health scores. It supports Quick, Standard, and Exhaustive plans to systematically validate end-to-end web app flows.

How do I verify ship-readiness before deploying a web app?

Verify ship-readiness by generating before and after health scores alongside a summary report. The structured QA process validates regression checks and UI interactions, providing clear guidance on whether your web application is ready for release.

Can I run a quick smoke test on my active web app repository?

Yes, you can run a quick smoke test by executing the QA command in your repository. This initiates a Quick testing plan that performs rapid verification against the active web application to catch immediate issues.

What do I need to reproduce and fix bugs through automated verification?

Reproducing and fixing bugs requires a reproducible test environment and clear issue reproduction steps. The skill then applies atomic commits for fixes and performs automated verification to ensure the regression is resolved.

What is the best way to maintain clean git history while fixing regressions?

Maintain clean git history by using atomic commits for each individual bug fix during the QA process. After each commit, the system re-verifies the fix, ensuring your feature branch remains stable and regression-free throughout development.

Does this structured QA testing work for both frontend and backend changes?

Yes, structured QA testing is suitable for validating both frontend and backend changes. It adapts to feature branches and regression validation, covering end-to-end flows and UI interactions across the entire web application stack.