Review requirements traceability, risk, and test strategy to generate QA reports.
npx skills add https://github.com/freitassph/aiox-core --skill aiox-qa-freitassph
Please help me install this Agent Skill. Skill: aiox-qa Source: https://github.com/freitassph/aiox-core/tree/main/.codex/skills/aiox-qa Command: npx skills add https://github.com/freitassph/aiox-core --skill aiox-qa-freitassph
It solves the risk of shipping weak or untraceable tests by helping teams design comprehensive test architecture and make evidence-based quality gate decisions.
Use Case: Before merging a feature, review a story to confirm it meets NFR expectations, assess testing risk, and generate a quality gate decision plus a fix request for developers.
Ask it to run a structured QA review by saying: "Use *review-build uncommitted" to generate a full QA report for the current work.
High-intent search queries and answers about installing and using this skill.
To review test strategy and ensure requirements traceability, you can load a QA source-of-truth persona to analyze story-level artifacts, assess testing risks, and generate structured QA reports with documented evidence.
You can generate a QA report and developer fix requests by triggering a structured review workflow that evaluates non-functional requirements, profiles delivery risks, and outputs actionable fix requests for developers.
Yes, you can use it for non-functional requirements assessment and quality gate decisions. It evaluates NFR expectations against project artifacts to produce pass, fail, or conditional quality gate decisions tied to a specific story.
The best way to document quality gates is by applying a deterministic review workflow that maps test architecture and risk assessment results directly to story-level artifacts, yielding a structured quality gate decision.
Yes, this test architecture review tool works without external dependencies. It operates entirely within declared project artifacts to produce evidence-based quality gate decisions and structured QA reviews.
You should not use an automated QA reporting workflow when your project lacks declared artifacts for requirements traceability, as the review mechanism relies on loading a source-of-truth persona bound to existing story-level documentation.
magnus919Automate formal SPEC.md authoring for AI-native SDD pipelines.
bychrisrEnforces quality gates and reviews test architecture for software development projects.
SynkraAIReview test architecture and make quality gate decisions for software projects.
hitoshisekiReviews test architecture and generates PASS, CONCERNS, FAIL, or WAIVED gate decisions.
