qa

Test web applications across end-to-end, regression, and feature validation tiers.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/JeremiahEllington/NoahEllington --skill qa-jeremiahellington
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa
Source: https://github.com/JeremiahEllington/NoahEllington/tree/main/.claude/skills/qa
Command: npx skills add https://github.com/JeremiahEllington/NoahEllington --skill qa-jeremiahellington

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams face slow feedback cycles between testing, defect discovery, and validating fixes. This Skill provides a disciplined workflow to systematically test a web application, capture before/after evidence, and re-verify changes, reducing regressions and release risk.

Core Features & Use Cases

  • End-to-end QA passes that cover quick, standard, and exhaustive tiers to align with risk tolerance.
  • Iterative bug fixing with atomic commits and re-verification to ensure changes are correct and traceable.
  • Ship-readiness reporting with health scores and evidence that informs release decisions.

Quick Start

Run a QA pass on the target URL and commit each fix atomically before re-verifying.

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 app?

You can automate end-to-end QA testing by running systematic validation passes that cover quick, standard, and exhaustive tiers to align with your risk tolerance and ensure ship-readiness.

What is the best way to fix bugs found during regression testing?

The best way to fix bugs found during regression testing is through iterative bug fixing with atomic commits, re-verifying each change individually to ensure corrections are correct and traceable.

How does ship-readiness reporting work for web application releases?

Ship-readiness reporting works by generating health scores and collecting before-and-after evidence from QA passes, informing release decisions by reducing regressions and providing traceable validation data.

Can I run a quick smoke test instead of an exhaustive QA check?

Yes, you can run a quick smoke test instead of an exhaustive check. The testing workflow supports multiple tiers from quick smoke tests to exhaustive checks, allowing you to align validation depth with risk tolerance.

How do I capture evidence during web app validation?

Evidence during web app validation is captured systematically as before-and-after snapshots throughout the testing workflow, satisfying automated test planning and supporting ship-readiness reporting.