aiox-qa

Audit story requirements and test strategy to produce QA gate decisions.

Updated May 8, 2026
One-click install
npx skills add https://github.com/Elevaria-bia/elevaria-bia.github.io --skill aiox-qa-elevaria-bia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-qa
Source: https://github.com/Elevaria-bia/elevaria-bia.github.io/tree/main/meu-projeto/.claude/skills/AIOX/agents/qa
Command: npx skills add https://github.com/Elevaria-bia/elevaria-bia.github.io --skill aiox-qa-elevaria-bia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents defects and quality regressions by performing structured, evidence-driven QA reviews and gate decisions before stories advance.

Core Features & Use Cases

  • Quality gate reviews: Produce PASS/CONCERNS/FAIL/WAIVED decisions with clear rationales and traceability to story requirements.
  • Risk and NFR validation: Assess risk profiles and validate non-functional requirements such as security, performance, reliability, and testability.
  • Test strategy and coverage: Create comprehensive test scenarios, map requirements to Given-When-Then traces, and generate QA fix requests for developers.
  • Use case: Before merge, review a story’s acceptance criteria and evidence readiness, scan for security and console issues, and generate a gate outcome plus actionable fixes.

Quick Start

Use the aiox-qa skill to run a comprehensive QA gate for story S-123 by instructing the assistant to execute: *gate S-123.

Frequently Asked Questions about aiox-qa

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

FAQPage Schema
How do I enforce a quality gate for pre-merge story reviews?

Risk-based QA testing prioritizes validation by assessing story risk profiles and mapping requirements to Given-When-Then traces. It generates comprehensive test scenarios and QA fix requests to target high-risk areas before software delivery.

What is requirements traceability in pre-merge quality gate reviews?

Requirements traceability in pre-merge reviews maps story acceptance criteria directly to test scenarios and Given-When-Then traces. This ensures strict gate governance by verifying evidence readiness and linking quality outcomes to specific requirements.

How do I validate non-functional requirements like security before a story merge?

To validate non-functional requirements before a merge, scan for security, performance, and reliability issues alongside console errors. This assessment checks risk profiles and produces actionable QA fix requests for developers to resolve.

Can I automate QA gate decisions for individual user stories?

Yes, you can automate QA gate decisions for individual stories by instructing the assistant to execute gate commands for specific story IDs. This triggers a comprehensive review of acceptance criteria, evidence, and security scans to output gate outcomes.

What are the limitations of automated pre-merge quality gate audits?

Automated pre-merge quality gate audits operate under strict QA result write-access limitations and focus strictly on pre-merge workflows. They require structured evidence and clear acceptance criteria to produce accurate risk-based prioritization and gate governance.