skills.rest
mattothomas
mattothomasCOMMUNITY
Explore all skills by this author →
GitHub

qa

Test web applications systematically, detect bugs, and validate fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA tests a web application systematically, detects bugs, and validates fixes.

Core Features & Use Cases

  • Systematic QA cycles with repeatable tests
  • Atomic commits for each bug fix and re-verification
  • Ship-readiness reporting with before/after health scores

Quick Start

Run a QA cycle on the target web app, fix each bug atomically, and re-verify until ship-ready.

Frequently Asked Questions about qa

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

FAQPage Schema
How do I automate web testing and verify bug fixes systematically?▼

Automated web testing runs repeatable test cycles, detects bugs, and re-verifies after each fix. It generates before and after evidence, calculates health scores, and reports ship-readiness to ensure your application is deployment ready.

What is ship-readiness reporting and how does it validate regression testing?▼

Ship-readiness reporting evaluates regression testing by producing before and after health scores. It validates each atomic bug fix through re-verification cycles, ensuring web application stability before deployment using generated test evidence.

Can I run targeted QA tests instead of exhaustive feature verification?▼

Yes, you can run quick targeted testing or exhaustive verification across features. Both modes detect bugs, validate fixes atomically, and generate structured QA reports with evidence for your web application.

Do I need Bash and file editing tools to generate QA evidence reports?▼

Yes, generating QA evidence reports requires Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion, and WebSearch tools. These tools execute tests, capture before and after evidence, and produce structured ship-readiness reports.

What is the best way to fix bugs atomically during a QA cycle?▼

The best way to fix bugs atomically is applying one fix per commit, then re-verifying tests immediately. This systematic QA cycle generates before and after health scores, confirming ship-readiness for each bug fix.

Can I generate a QA report without running new tests?▼

Yes, a /qa-only mode supports report-only runs. It generates structured QA documentation and ship-readiness health scores from existing test evidence without executing new bug detection or verification cycles.

Related Skills

Explore More Software Engineering Skills→
papeete-consulting-labpapeete-consulting-lab

test-app

Coordinate automated testing and verification reporting for CHANNEL-zone web applications.

Official
Advanced
oborchersoborchers
28

tag-based-production-deploys

Enforce git tag-based production deployments with manual approval gates.

Community
Advanced
kinetaskinetas

qa

Automate web application testing and guide bug fixes with atomic commits.

Community
Advanced
scanbottscanbott

qa

Run end-to-end web application tests and verify fixes across environments.

Community
Advanced