skills.rest
Scivor
ScivorCOMMUNITY
Explore all skills by this author →
Website𝕏@Scivor_AIGitHub

qa

Automate web application testing and verify fixes across iterative cycles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA is a systematic process to test a web application and fix bugs found. It reduces manual toil, speeds up feedback cycles, and helps ensure changes don't regress critical paths.

Core Features & Use Cases

  • Automated web-app testing that detects regressions and collects evidence.
  • Iterative bug fixing with atomic commits and re-verification to ship stable releases.
  • Tiered testing strategies (Quick, Standard, Exhaustive) to balance time and coverage.

Quick Start

Ask me to run QA on the target app with /qa and I will start the tiered QA cycle and begin fixes.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate web app testing and fix regressions iteratively?▼

Run automated QA testing using tiered strategies like Quick, Standard, or Exhaustive to detect regressions and collect evidence, then re-verify fixes iteratively. Trigger the process via /qa to balance time and coverage while shipping stable releases.

What is the best way to balance test coverage and execution time for web automation?▼

Use tiered testing strategies to balance coverage and execution time for web automation. Select Quick, Standard, or Exhaustive tiers to scale defect detection and regression verification depth based on your release cycle requirements.

Can I run automated regression testing without writing custom test scripts?▼

Yes, you can run automated regression testing without custom scripts by triggering the QA cycle via /qa or /qa-only commands. The process autonomously handles defect detection, iterative bug fixing, and ship-readiness summaries for your web application.

How does automated bug fixing verify that code changes don't break critical paths?▼

Automated bug fixing verifies critical paths through iterative cycles that apply atomic commits and re-verify fixes. It targets regression verification and produces evidence-rich health reporting to confirm critical web app functionalities remain stable.

When should I use the exhaustive testing tier instead of the standard tier?▼

Use the exhaustive testing tier when preparing for major releases requiring maximum defect detection and regression verification. The standard tier suits routine iterative bug fixing, while exhaustive testing provides deeper evidence-rich health reporting.

Related Skills

Explore More Software Engineering Skills→
moogieonmoogieon

qa

Automate QA testing and iteratively fix bugs in web application source code.

Community
Advanced
wednesday-solutionswednesday-solutions
165

deploy-checklist

Verify pre-deploy prerequisites and post-deploy health for production deployments.

Official
Intermediate
puwenjunluck-pixelpuwenjunluck-pixel

fix

Automate bug fixing with root cause analysis and regression testing.

Community
Advanced
distribucionesfayosmoreno-sysdistribucionesfayosmoreno-sys

ui-visual-validator

Validate UI modifications for visual regression, compliance, and accessibility.

Community
Advanced