skills.rest
lachieh
lachiehCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa

Identifies and verifies web app changes through tiered QA tests and commits fixes with re-verification.

Updated Mar 15, 2026
Search Tags:#automation#testing#e2e#qa#regression#bug-fix#web-app
One-click install
npx skills add https://github.com/lachieh/babytalk --skill qa-lachieh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/lachieh/babytalk/tree/main/.claude/skills/gstack/qa
Command: npx skills add https://github.com/lachieh/babytalk --skill qa-lachieh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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". Proactively suggest when the user says a feature is ready for testing or asks "does this work?". Three tiers: Quick (critical/high only), Standard (+ medium), Exhaustive (+ cosmetic). Produces before/after health scores, fix evidence, and a ship-readiness summary. For report-only mode, use /qa-only.

Core Features & Use Cases

  • Structured QA testing flow with three tiers: Quick, Standard, Exhaustive.
  • Automated evidence gathering, before/after health scores, and ship-readiness summaries.
  • Atomic commits and re-verification cycles to ensure traceable fixes.

Quick Start

Run a full QA pass on the current project by invoking the qa skill in the CLI.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate web application QA testing and bug fixing in one workflow?▼

Automated QA testing identifies and verifies changes in a web application by running structured tests, fixing bugs iteratively, and committing atomic fixes with re-verification. It generates before/after health scores, fix evidence, and a ship-readiness summary.

What is the best way to structure e2e regression tests before a release?▼

Structure e2e regression tests using a tiered approach: Quick for critical and high-priority bugs only, Standard to include medium issues, and Exhaustive to cover cosmetic defects. This prioritizes tests effectively on feature branches and releases.

Can I run QA tests and generate a report without automatically modifying code?▼

Yes, you can run QA tests and generate a report without modifying code by using the report-only mode. This mode performs the structured testing and evidence gathering without applying the iterative bug fixes to your source code.

How does automated bug fixing verify that source code changes are safe to ship?▼

Automated bug fixing verifies changes by committing fixes atomically and running re-verification cycles. It produces before and after health scores alongside fix evidence, providing a clear ship-readiness summary to confirm the web application is stable.

When should I use an exhaustive testing tier over a quick QA pass?▼

Use the exhaustive testing tier when you need to verify cosmetic defects alongside critical and medium issues, typically before a major release. Use the quick tier for fast feedback on feature branches when only critical and high-priority bugs matter.

Related Skills

Explore More Software Engineering Skills→
GS-PersonalGS-Personal

qa

Automate web application QA testing across four modes and generate structured health reports.

Official
Advanced
shaythegay13shaythegay13

qa

QA test web applications, fix bugs, and commit fixes atomically.

Community
Advanced
makyua-sanmakyua-san

qa

Run tiered QA tests on web applications and commit atomic fixes.

Community
Advanced
NimbleBrainIncNimbleBrainInc
2

qa-tester

Design QA strategies and test cases for web, API, and mobile applications.

Official
Basic