skills.rest
2300031147
2300031147COMMUNITY
Explore all skills by this author →
GitHub

qa

Run tiered QA tests on web applications and fix bugs with atomic commits.

Updated Apr 12, 2026
Search Tags:#automation#testing#qa#quality-assurance#atomic-commits#web-application#bug-fix
One-click install
npx skills add https://github.com/2300031147/clawopencode --skill qa-2300031147
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/2300031147/clawopencode/tree/main/skills/qa
Command: npx skills add https://github.com/2300031147/clawopencode --skill qa-2300031147

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". 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. (gstack)

Core Features & Use Cases

  • Systematically QA test a web application and fix bugs with atomic commits and re-verification.
  • Proactively suggest when features are ready for testing or when feedback indicates a need for QA validation.
  • Three-tier testing strategy (Quick, Standard, Exhaustive) with health scoring and ship-readiness reporting.

Quick Start

Tell the AI to start a QA run for the current project: "qa run now" or "qa test this site".

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 fixes for a web application?▼

Automated QA testing for web applications runs comprehensive tests, iteratively fixes source code bugs, commits each fix atomically, and re-verifies results. It produces health scores and ship-readiness reports.

What is the best way to run an exhaustive web application test and fix what's broken?▼

Exhaustive web application testing covers critical, high, medium, and cosmetic issues, iteratively fixing what's broken with atomic commits. It produces before and after health scores with fix evidence.

Can I generate a QA report only without automatically modifying my source code?▼

Yes, you can generate a QA report only without automatic source code modification by using the report-only mode. This runs testing and health scoring without applying iterative bug fixes.

How do atomic commits work during iterative bug fixing?▼

Atomic commits during iterative bug fixing isolate each source code change into a single verifiable commit. After finding a bug, the fix is committed individually and re-verified before moving to the next.

What is the difference between quick, standard, and exhaustive QA testing tiers?▼

Quick QA testing targets critical and high severity bugs, Standard adds medium severity, and Exhaustive includes cosmetic issues. All tiers generate health scores, fix evidence, and ship-readiness summaries.

Related Skills

Explore More Software Engineering Skills→
Jia-Hong-PengJia-Hong-Peng

design-review

Detect visual design inconsistencies and commit atomic fixes with screenshots.

Community
Advanced
ligianehualigianehua

qa

Test web applications end-to-end and fix defects with atomic commits.

Community
Advanced
puwenjunluck-pixelpuwenjunluck-pixel

fix

Automate bug fixing with root cause analysis and regression testing.

Community
Advanced
reomgitreomgit

qa-only

Test web applications and generate detailed QA reports with repro steps.

Community
Intermediate