skills.rest
JonOlsenCa
JonOlsenCaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa

Run end-to-end QA tests on web applications and guide iterative bug fixes.

Updated Aug 27, 2026
Search Tags:#automation#testing#qa#verification#ci-cd#bug-fix#web-app
One-click install
npx skills add https://github.com/JonOlsenCa/gstack-main --skill qa-jonolsenca
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/JonOlsenCa/gstack-main/tree/main/qa
Command: npx skills add https://github.com/JonOlsenCa/gstack-main --skill qa-jonolsenca

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.

Core Features & Use Cases

  • Systematic QA testing of a web application and guided bug fixing workflow.
  • Atomic commits for each fix and re-verification to ensure traceability.
  • Proactive suggestions and tiered testing coverage with before/after health scores.

Quick Start

Run the QA workflow with /qa to begin a test pass on the current project.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate end-to-end QA testing for a web application?▼

Automate end-to-end QA testing by running the workflow on your web application, which executes test passes, identifies bugs, and generates before/after health scores. It systematically tests the site and iteratively fixes discovered bugs in the source code.

How does automated bug fixing work during QA testing?▼

Automated bug fixing works by iteratively applying source code corrections for discovered issues and re-verifying them. Each correction is committed atomically to ensure traceability, providing fix evidence and confirming the bug is resolved before moving on.

Can I generate a ship-readiness report without applying source code fixes?▼

Yes, you can generate a ship-readiness report without applying fixes by using the /qa-only mode. This report-only mode runs the testing pass and outputs health scores and bug findings without modifying your web application's source code.

What levels of testing coverage are available for finding web app bugs?▼

Available testing coverage includes three tiers: Quick for critical and high severity bugs, Standard which adds medium severity issues, and Exhaustive which includes cosmetic bugs. These tiers determine the depth of your bug finding and verification pass.

What is the best way to verify a web feature is ready for production?▼

The best way to verify production readiness is to run a structured QA workflow that produces a ship-readiness summary. It evaluates the web application, generates health scores, and provides fix evidence to confirm the feature works as intended.

Related Skills

Explore More Software Engineering Skills→
AndrewLi0420AndrewLi0420

qa

Run automated QA passes on web applications and fix detected bugs.

Community
Advanced
SjdjdiejdrirhdkjejSjdjdiejdrirhdkjej

production-deployment-phase

Promote validated staging builds to production with semantic versioning and health checks.

Community
Advanced
jm199seojm199seo

land-and-deploy

Merge PRs, deploy to production, and verify canary health after CI.

Community
Advanced
benrapportbenrapport

qa

Automate end-to-end QA testing and bug fixing for web applications.

Community
Advanced