qa-tester

Enforce evidence-based QA with PASS/FAIL reporting during BUILD and EXECUTE stages.

3|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/jwm-axoni/auggie-pai --skill qa-tester-jwm-axoni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-tester
Source: https://github.com/jwm-axoni/auggie-pai/tree/main/skills/qa-tester
Command: npx skills add https://github.com/jwm-axoni/auggie-pai --skill qa-tester-jwm-axoni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quality assurance validation is necessary to systematically uncover edge cases, validate behavior, and produce objective PASS/FAIL reporting during software development.

Core Features & Use Cases

  • Overlay persona to enforce rigorous QA during BUILD and EXECUTE phases
  • Systematic edge-case taxonomy, evidence collection, and reproducible tests
  • Structured reporting formats with PASS/FAIL/PARTIAL outcomes and actionable feedback

Quick Start

Activate the qa-tester persona overlay and run a validation pass on your current task, collecting evidence and generating a PASS/FAIL report.

Frequently Asked Questions about qa-tester

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

FAQPage Schema
How do I validate edge-case behavior in software with evidence-based QA?

Edge-case validation applies structured testing protocols to capture evidence and reproduce failures. This generates objective PASS/FAIL reporting across builds and features during the BUILD and EXECUTE stages.

What is the best way to reproduce failure scenarios during development workflows?

Reproducible failure scenarios are generated through systematic evidence collection and adversarial testing. This process identifies edge-case taxonomy and verifies behavior using structured validation protocols.

How do I generate PASS/FAIL reports across builds and features?

PASS/FAIL reporting is produced by enforcing structured validation passes during software development. These reports include PASS, FAIL, or PARTIAL outcomes alongside actionable feedback for feature validation.

Does this QA testing approach require specific dependencies or components?

No dependencies or components are required to apply this QA testing approach. It functions as a persona overlay that enforces rigorous validation and evidence collection directly within existing development workflows.

When do I need adversarial testing for reproducible failure reproduction?

Adversarial testing is needed when uncovering edge-case behavior requires objective validation. It enforces evidence-based QA to systematically identify, validate, and reproduce failures across builds and features.

What limitations exist when applying edge-case taxonomy during the BUILD and EXECUTE phases?

Edge-case taxonomy validation focuses strictly on the BUILD and EXECUTE stages. It requires structured evidence collection to generate accurate PASS/FAIL outcomes, limiting its scope to reproducible software quality verification.